Devices, methods, and user interfaces for interacting with user interface objects via proximity-based and contact-based inputs

ABSTRACT

An electronic device with a touch-sensitive surface, a display, one or more first sensors to detect proximity of an input object above the touch-sensitive surface and one or more second sensors to detect intensity of contact of the input object with the touch-sensitive surface displays a user interface object at a first location, and detects selection of the user interface object at the first location on the display. While the user interface object is selected, the device detects lateral movement of the input object over the touch-sensitive surface while the input object meets hover criteria. In response, the device moves the selected user interface object in accordance with the lateral movement. While moving the selected user interface object, the device dynamically varies a first visual characteristic of the selected user interface object in accordance with a current hover proximity parameter of the input object.

RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application Ser.No. 62/506,502, filed May 15, 2017, titled “Devices, Methods, and UserInterfaces for Interacting with User Interface Objects viaProximity-based and Contact-based Inputs,” and to U.S. ProvisionalApplication Ser. No. 62/399,239, filed Sep. 23, 2016, titled “Devices,Methods, and User Interfaces for Interacting with User Interface Objectsvia Proximity-based and Contact-based Inputs,” which are incorporated byreference in their entireties.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that facilitate user interface interactionsthrough proximity-based and contact-based inputs.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Exemplary touch-sensitive surfaces include touchpads andtouch-screen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

Some touch-sensitive surfaces also include sensors that detect inputsprovided by an object (e.g., stylus) that is not in direct contact withthe touch-sensitive surface, but is in close proximity to thetouch-sensitive surface. The proximity-based inputs provide anadditional avenue for manipulating user interface objects on a display.However, contact-based inputs and proximity-based inputs do not oftenwork together seamlessly and may interfere with each other and causeconfusion and frustration to the user.

Exemplary manipulations of user interface objects include adjusting theposition and/or size of one or more user interface objects or activatingbuttons or opening files/applications represented by user interfaceobjects, as well as associating metadata with one or more user interfaceobjects or otherwise manipulating user interfaces. Exemplary userinterface objects include digital images, video, text, icons, andcontrol elements such as buttons and other graphics. A user will, insome circumstances, need to perform such manipulations on user interfaceobjects in, for example, a note taking application, a file managementprogram, an image management application, a digital content managementapplication, a drawing application, a presentation application, a wordprocessing application, or a spreadsheet application.

But methods for performing these manipulations are cumbersome andinefficient. In addition, these methods take longer than necessary,thereby wasting energy. This latter consideration is particularlyimportant in battery-operated devices.

SUMMARY

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for interacting with user interfaces toperform operations using contact-based and proximity-based inputs. Suchmethods and interfaces optionally complement or replace conventionalmethods for interacting with user interfaces using contact-based andproximity-based inputs. Such methods and interfaces reduce the number,extent, and/or nature of the inputs from a user and produce a moreefficient human-machine interface. For battery-operated devices, suchmethods and interfaces conserve power and increase the time betweenbattery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch-screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through stylus and/or fingercontacts and gestures on the touch-sensitive surface. In someembodiments, the functions optionally include image editing, drawing,presenting, word processing, website creating, disk authoring,spreadsheet making, game playing, telephoning, video conferencing,e-mailing, instant messaging, workout support, digital photographing,digital videoing, web browsing, digital music playing, note taking,and/or digital video playing. Executable instructions for performingthese functions are, optionally, included in a non-transitory computerreadable storage medium or other computer program product configured forexecution by one or more processors.

In accordance with some embodiments, a method is performed at anelectronic device with a touch-sensitive surface and a display, wherethe electronic device includes one or more first sensors to detectproximity of an input object above the touch-sensitive surface andoptionally one or more second sensors to detect intensity of contact ofthe input object with the touch-sensitive surface. The method includesdisplaying a user interface object at a first location on the display,and detecting selection of the user interface object at the firstlocation on the display. While the user interface object is selected,the method further includes detecting lateral movement of the inputobject over the touch-sensitive surface while the input object meetshover criteria. In response to detecting lateral movement of the inputobject over the touch-sensitive surface while the input object meets thehover criteria, the method includes moving the selected user interfaceobject in accordance with the lateral movement of the input object overthe touch-sensitive surface. While moving the selected user interfaceobject in accordance with the lateral movement of the input object overthe touch-sensitive surface, the method further includes dynamicallyvarying a first visual characteristic of the selected user interfaceobject in accordance with a current hover proximity parameter of theinput object.

In accordance with some embodiments, a method is performed at anelectronic device with a touch-sensitive surface and a display, wherethe device includes one or more first sensors to detect proximity of aninput object above the touch-sensitive surface and optionally one ormore second sensors to detect intensity of contact of the input objectwith the touch-sensitive surface. The method includes displaying a userinterface object at a first location on the display. While displayingthe user interface object at the first location on the display, themethod further includes detecting a first portion of an input by aninput object, where detecting the first portion of the input includesdetecting the input object at a location over the touch-sensitivesurface that corresponds to the first location of the user interfaceobject on the display while the input object meets hover criteria. Inresponse to detecting the first portion of the input, the methodincludes dynamically changing an appearance of the user interface objectin a first manner in accordance with a current hover proximity parameterof the input object. After dynamically changing the appearance of theuser interface object in a first manner in accordance with the currenthover proximity parameter of the input object, the method furtherincludes detecting a second portion of the input by the input object,where detecting the second portion of the input includes detecting theinput object making contact with the touch-sensitive surface at aninitial contact location that corresponds to the first location on thedisplay; and, in response to detecting the second portion of the input,dynamically changing the appearance of the user interface object in asecond manner in accordance with a current intensity of a contact by theinput object on the touch-sensitive surface.

In accordance with some embodiments, a method is performed at anelectronic device with a touch-sensitive surface and a display, wherethe electronic device includes one or more first sensors to detectproximity of an input object above the touch-sensitive surface, andoptionally one or more second sensors to detect intensity of contactswith the touch-sensitive surface. The method includes displaying aposition indicator within text on the display while an input objectabove the touch-sensitive surface meets hover criteria. While theposition indicator is displayed within the text on the display, themethod includes detecting a first movement of the input object thatincludes a component of movement parallel to the touch-sensitivesurface, where the input object continues to meet the hover criteriaduring the first movement. In response to detecting the first movementof the input object over the touch-sensitive surface, the methodincludes moving the position indicator within the displayed text inaccordance with the first movement of the input object. After moving theposition indicator within the displayed text in accordance with thefirst movement of the input object, the method includes detecting asecond movement of the input object that includes a component ofmovement parallel to the touch-sensitive surface; and, in response todetecting the second movement of the input object across thetouch-sensitive surface: in accordance with a determination that thesecond movement of the input object is detected while the input objectis in contact with the touch-sensitive surface, selecting text inaccordance with the second movement of the input object across thetouch-sensitive surface while the input object remains in contact withthe touch-sensitive surface.

A method is performed at a device having a display and a touch-sensitivesurface, wherein the device includes one or more first sensors fordetecting proximity of an input object above the touch-sensitivesurface. The method includes: displaying a user interface on thedisplay; detecting a first input by the input object that corresponds toa start of a first user interface operation; after detecting the firstinput that corresponds to the start of the first user interfaceoperation and while the input object meets hover proximity criteria,detecting lateral movement of the input object; in response to detectingthe lateral movement of the input object while the input object meetsthe hover proximity criteria, updating the user interface to indicate apreview of the first user interface operation; while the user interfaceis updated to indicate the preview of the first user interfaceoperation, detecting that the input object no longer meets the hoverproximity criteria; and, in response to detecting that the input objectno longer meets the hover proximity criteria: in accordance with adetermination that the input object no longer meets the hover proximitycriteria because the input object has exited a hover proximity range ofthe touch-sensitive surface, cancelling the first user interfaceoperation; and in accordance with a determination that the input objectno longer meets the hover proximity criteria because the input objecthas made contact with the touch-sensitive surface, confirming the firstuser interface operation.

A method is performed at a device having a display and a touch-sensitivesurface, wherein the device includes one or more first sensors fordetecting proximity of an input object above the touch-sensitivesurface. The method includes: displaying a first user interface objectat a first location on the display; detecting a predefined interactionwith the first user interface object by the input object; in response todetecting the predefined interaction with the first user interfaceobject by the input object, displaying a second user interface objectthat is associated with the first user interface object; whiledisplaying the second user interface object, detecting a change in ahover proximity parameter of the input object; and, in response todetecting the change in the hover proximity parameter of the inputobject: in accordance with a determination that the input object meetscontinue-to-display criteria, wherein the continue-to-display criteriarequire that the input object continues to meet hover proximity criteriain order for continue-to-display criteria to be met, maintaining displayof the second user interface object; and in accordance with adetermination that the input object meets cease-to-display criteria,wherein the cease-to-display criteria require that the input object nolonger meets the hover proximity criteria in order for thecease-to-display criteria to be met, ceasing to display the second userinterface object.

A method is performed at a device having a display and a touch-sensitivesurface, wherein the device includes one or more first sensors fordetecting proximity of an input object above the touch-sensitivesurface. The method includes: displaying a first user interface on thedisplay; while displaying the first user interface on the display,detecting that first hover proximity criteria are met by the inputobject, wherein the first hover proximity criteria require that acurrent value of a hover proximity parameter of the input object iswithin a first value range in order for the first hover proximitycriteria to be met; in response to detecting that the first hoverproximity criteria are met by the input object, displaying first visualfeedback that is associated with the first hover proximity criteria;while displaying the first visual feedback that is associated with thefirst hover proximity criteria, detecting a change in the current valueof the hover proximity parameter of the input object and that secondhover proximity criteria are met by the input object after the change,wherein the second hover proximity criteria require that the currentvalue of the hover proximity parameter of the input object is within asecond value range that is within the first value range in order for thesecond hover proximity criteria to be met; and in response to detectingthat the second hover proximity criteria are met by the input object,displaying second visual feedback, distinct and non-continuous from thefirst visual feedback, that is associated with the second hoverproximity range.

A method is performed at a device having a display and a touch-sensitivesurface, wherein the device includes one or more first sensors fordetecting proximity of an input object above the touch-sensitivesurface. The method includes: displaying, in a first user interface, aplurality of user interface objects that includes at least a first userinterface object; while displaying the plurality of user interfaceobjects, detecting an input object at a first hover location over thefirst user interface object that meets first hover proximity criteria;after detecting the input object at the first hover location over thefirst user interface object that meets the first hover proximitycriteria, detecting movement of the input object away from the firsthover location; in response to detecting movement of the input objectaway from the first hover location: in accordance with a determinationthat the input object meets first augmented hover proximity criteria,wherein the first augmented hover proximity criteria require that theinput object had met the first hover proximity criteria and anadditional requirement that augments the first hover proximity criteriabefore the input object moved away from the first location, performing afirst operation associated with the movement of the input object; and inaccordance with a determination that the input object does not meet thefirst augmented hover proximity criteria, forgoing performing the firstoperation.

A method is performed at a device having a display and a touch-sensitivesurface, wherein the device includes one or more first sensors fordetecting proximity of an input object above the touch-sensitive surfaceand one or more second sensors for detecting intensity of contacts withthe touch-sensitive surface. The method includes: displaying a pluralityof user interface objects, including a first user interface object, onthe display; detecting a first portion of an input by an input object,including detecting the input object at a first hover location above thetouch-sensitive surface while the input object meets first hoverproximity criteria, wherein the first hover location above thetouch-sensitive surface corresponds to a location of the first userinterface object on the display; in response to detecting the firstportion of the input, including detecting the input object at the firsthover location above the touch-sensitive surface while the input objectmeets the first hover proximity criteria: in accordance with adetermination that the first user interface object has differentiatedresponses to intensity-based inputs, displaying first visual feedback inassociation with the first user interface object to indicate that thefirst user interface object has differentiated responses tointensity-based inputs; and, in accordance with a determination that thefirst user interface object does not have differentiated responses tointensity-based inputs, foregoing displaying the first visual feedbackin association with the first user interface object.

A method is performed at a device having a display and a touch-sensitivesurface, wherein the device includes one or more first sensors fordetecting proximity of an input object above the touch-sensitivesurface. The method includes: displaying a content selection objectwithin selectable content, wherein the content selection object includesa first edge of the content selection object and a second edge of thecontent selection object, and wherein content located between the firstedge of the content selection object and the second edge of the contentselection object is selected; detecting a first portion of an input bythe input object, including detecting the input object at a first hoverlocation above the touch-sensitive surface that corresponds to the firstedge of the content selection object; and in response to detecting thefirst portion of the input by the input object: in accordance with adetermination that the first portion of the input meets first criteria,wherein the first criteria require that the input object meets hoverproximity criteria when the input object is detected at the first hoverlocation above the touch-sensitive surface that corresponds to thelocation of the first edge of the content selection object on thedisplay in order for the first criteria to be met, changing anappearance of the first edge relative to the second edge of the contentselection object in a first manner to indicate that the first edge ofthe content selection object will be selected for movement relative tothe second edge of the content selection object when the input objectmeets second criteria.

A method is performed at a device having a display and a touch-sensitivesurface, wherein the device includes one or more first sensors fordetecting proximity of an input object above the touch-sensitivesurface. The method includes: displaying a plurality of user interfaceobjects on the display, wherein the plurality of user interface objectsinclude a first user interface object and a second user interfaceobject, and wherein the first user interface object and the second userinterface object are displayed at different locations on the display;detecting the input object at a first hover location above a firstportion of the touch-sensitive surface while the input object meetshover proximity criteria; in response to detecting the input object atthe first hover location above the first portion of the touch-sensitivesurface while the input object meets the hover proximity criteria,placing input focus on the first user interface object; while the firstuser interface object has input focus and while the input objectcontinues to meet the hover proximity criteria, detecting a respectivemovement of the input object from the first hover location above thefirst portion of the touch-sensitive surface to a respective hoverlocation above a respective portion of the touch-sensitive surface thatis different from the first portion of the touch-sensitive surface; andin response to detecting the respective movement of the input objectwhile the input object continues to meet the hover proximity criteria:in accordance with a determination that the respective movement is afirst movement from the first hover location to a second hover locationthat is above a second portion of the touch-sensitive surface: inaccordance with a determination that the first movement meets firstfocus-maintenance criteria, wherein the first focus-maintenance criteriarequire that the first movement includes less than a first thresholdamount of lateral movement in order for the first focus-maintenancecriteria to be met, and wherein the first threshold amount of lateralmovement is determined based on a value of a characteristic hoverproximity parameter of the input object during the first movement of theinput object from the first hover location to the second hover location,maintaining input focus on the first user interface object; and inaccordance with a determination that the first movement meets firstfocus-shifting criteria, wherein the first focus-shifting criteriarequire that the first movement includes at least the first thresholdamount of lateral movement in order for the first focus-shiftingcriteria to be met, shifting input focus from the first user interfaceobject to the second user interface object.

In accordance with some embodiments, an electronic device includes adisplay, a touch-sensitive surface, one or more sensors to detectproximity of an input object above the touch-sensitive surface, andoptionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface, one or more processors, memory, and one or moreprograms; the one or more programs are stored in the memory andconfigured to be executed by the one or more processors and the one ormore programs include instructions for performing or causing performanceof the operations of any of the methods described herein. In accordancewith some embodiments, a computer readable storage medium has storedtherein instructions which when executed by an electronic device with adisplay, a touch-sensitive surface, one or more sensors to detectproximity of an input object above the touch-sensitive surface, andoptionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface, cause the device to perform or causeperformance of the operations of any of the methods described herein. Inaccordance with some embodiments, a graphical user interface on anelectronic device with a display, a touch-sensitive surface, one or moresensors to detect proximity of an input object above the touch-sensitivesurface, optionally one or more sensors to detect intensity of contactswith the touch-sensitive surface, a memory, and one or more processorsto execute one or more programs stored in the memory includes one ormore of the elements displayed in any of the methods described herein,which are updated in response to inputs, as described in any of themethods described herein. In accordance with some embodiments, anelectronic device includes: a display, a touch-sensitive surface, one ormore sensors to detect proximity of an input object above thetouch-sensitive surface, and optionally one or more sensors to detectintensity of contacts with the touch-sensitive surface; and means forperforming or causing performance of the operations of any of themethods described herein. In accordance with some embodiments, aninformation processing apparatus, for use in an electronic device with adisplay and a touch-sensitive surface, one or more sensors to detectproximity of an input object above the touch-sensitive surface, andoptionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface, includes means for performing or causingperformance of the operations of any of the methods described herein.

Thus, electronic devices with displays, touch-sensitive surfaces, one ormore sensors to detect proximity of an input object above thetouch-sensitive surface, and optionally one or more sensors to detectintensity of contacts with the touch-sensitive surface are provided withfaster, more efficient methods and interfaces for interacting with auser interface to perform operations through proximity-based andcontact-based inputs, thereby increasing the effectiveness, efficiency,and user satisfaction with such devices. Such methods and interfaces maycomplement or replace conventional methods for interacting with a userinterface through proximity-based and contact-based inputs.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4 is a block diagram of an exemplary electronic stylus inaccordance with some embodiments.

FIGS. 5A-5B illustrate a positional state of a stylus relative to atouch-sensitive surface in accordance with some embodiments

FIG. 6A illustrates an example user interface for a menu of applicationson a portable multifunction device in accordance with some embodiments.

FIG. 6B illustrates an example user interface for a multifunction devicewith a touch-sensitive surface that is separate from the display inaccordance with some embodiments.

FIGS. 7A-7U illustrate exemplary user interfaces for interacting with auser interface object through proximity-based and contact-based inputs(e.g., pulling, picking up, dragging, and dropping off a user interfaceobject) in accordance with some embodiments.

FIGS. 7V-7AJ illustrate exemplary user interfaces for interacting with auser interface object through proximity-based and contact-based inputs(e.g., pushing toward, pressing against, easing off of, and pulling awayfrom the user interface object) in accordance with some embodiments.

FIGS. 7AK-7AU illustrate exemplary user interfaces for interacting witha user interface object through proximity-based and contact-based inputs(e.g., moving a cursor and selecting text) in accordance with someembodiments.

FIGS. 8A-8V illustrate exemplary user interfaces for displaying apreview of a move operation by a hover-move input, and canceling orconfirm the move operation in accordance with a determination of whetherthe input object has made contact with the touch-sensitive surfacebefore being lifted out of the hover proximity range, in accordance withsome embodiments.

FIGS. 9A-9O illustrate exemplary user interfaces for displaying a userinterface object after predefined user interface interaction by theinput object, and conditionally maintaining display of the userinterface object while the input object continue to meet hover proximitycriteria, in accordance with some embodiments.

FIGS. 10A-10Y illustrate exemplary user interfaces for displayingdifferent visual feedback when an input object is detected to meetdifferent levels of hover proximity criteria, in accordance with someembodiments.

FIGS. 11A-11J illustrate exemplary user interfaces for entering aninformation display mode after the input object meets augmented hoverproximity criteria, and while in the information display mode,displaying information for additional objects while the input objectmeets non-augmented hover proximity criteria, in accordance with someembodiments.

FIGS. 12A-12R illustrate exemplary user interfaces for displaying visualfeedback indicating whether an object has differentiated,object-specific responses for intensity-based inputs, when an inputobject hovers over the object, in accordance with some embodiments.

FIGS. 13A-13N illustrate exemplary user interfaces for indicating whichselection handle of a selection object is selected for movement when aninput object hovers over the selection object, in accordance with someembodiments.

FIGS. 14A-14M illustrate maintaining input focus on an object during ahover move input, where the criteria for maintaining input focus on theobject is dynamically changed based on a characteristic hover proximityparameter of the input object during the hover move input, in accordancewith some embodiments.

FIGS. 15A-15C are flow diagrams illustrating a method of interactingwith a user interface object through proximity-based and contact-basedinputs in accordance with some embodiments.

FIGS. 16A-16E are flow diagrams illustrating a method of interactingwith a user interface object through proximity-based and contact-basedinputs in accordance with some embodiments.

FIGS. 17A-17C are flow diagrams illustrating a method of interactingwith a user interface object through proximity-based and contact-basedinputs in accordance with some embodiments.

FIGS. 18A-18G are flow diagrams illustrating a method of moving anobject by a hover move input, in accordance with some embodiments.

FIGS. 19A-19E are flow diagrams illustrating a method of maintainingdisplay of a transient user interface object using a hover input, inaccordance with some embodiments.

FIGS. 20A-20I are flow diagrams illustrating a method of displayingdifferent visual feedback when a hover input meets different levels ofhover proximity criteria, in accordance with some embodiments.

FIGS. 21A-21D are flow diagrams illustrating a method of performing anoperation after augmented hover proximity criteria have been met, inaccordance with some embodiments.

FIGS. 22A-22G are flow diagrams illustrating a method of displayingvisual feedback in response to a hover input to identify a userinterface object that has differentiated responses to intensity-basedinputs, in accordance with some embodiments.

FIGS. 23A-23E are flow diagrams illustrating a method of visuallyindicating an edge of a selection object that will be selected formovement, in response to a hover input, in accordance with someembodiments.

FIGS. 24A-24E are flow diagrams illustrating a method of maintaininginput focus on an object based on whether an input object has made morethan a threshold amount of lateral movement, where the threshold amountof lateral movement is determined based on a characteristic hoverproximity parameter of an input object, in accordance with someembodiments.

DESCRIPTION OF EMBODIMENTS

Proximity-based inputs and contact-based inputs are provided tomanipulate a user interface object. Visual, haptic, and/or audiofeedback is provided in accordance with whether a user interface objectis under the influence of a proximity-based input (e.g., the userinterface object being in a hover state under the influence of a hoverinput) or a contact-based input (e.g., the user interface object beingin a contact state under the influence of a press input or swipe input).Visual, haptic, and/or audio feedback is optionally provided when theuser interface object transitions between the hover state and thecontact state. The device dynamically changes the feedback provided tothe user based on input metrics such as hover proximity parameters andintensities of contact.

In some embodiments, a user interface object is moved by a hover input,and the device changes the appearance of the user interface object basedon the hover proximity parameter of the hover input. In someembodiments, when a continuous input includes one or moreproximity-based inputs and one or more contact-based inputs, the devicechanges the appearance of the user interface object in accordance withthe hover-proximity parameters of the proximity-based inputs and inaccordance with the intensities of the contact-based inputs, such thatthe changes in at least one characteristic is a smooth change when theuser interface object transitions between the hover state and thecontact state. In some embodiments, an input object (e.g., a finger orstylus) places a cursor within text at a location in accordance withlateral movement of the input object above the touch-sensitive surface,and starts expanding text selection from the cursor location inaccordance with lateral movement of the input object across thetouch-sensitive surface.

Below, FIGS. 1A-1B, 2, and 3 provide a description of exemplary devices.FIG. 4 provides a description of an exemplary electronic stylus. FIGS.5A-5B illustrate a positional state of a stylus relative to atouch-sensitive surface. FIGS. 6A-6B, FIGS. 7A-7AU, FIGS. 8A-8V, FIGS.9A-9O, FIGS. 10A-10Y, FIGS. 11A-11J, FIGS. 12A-12R, FIGS. 13A-13N, andFIGS. 14A-14L illustrate exemplary user interfaces for interacting witha user interface object through proximity-based inputs and contact-basedinputs. FIGS. 15A-15C, FIGS. 16A-16E, FIGS. 17A-17C, FIGS. 18A-18G,FIGS. 19A-19E, FIGS. 20A-20I, FIGS. 21A-21D, FIGS. 22A-22G, FIGS.23A-23E, and 24A-24E illustrate flow diagrams of methods of interactingwith a user interface object through proximity-based and contact-basedinputs. The user interfaces in FIGS. 6A-6B, FIGS. 7A-7AU, FIGS. 8A-8V,FIGS. 9A-9O, FIGS. 10A-10Y, FIGS. 11A-11J, FIGS. 12A-12R, FIGS. 13A-13N,and FIGS. 14A-14L are used to illustrate the processes in FIGS. 15A-15C,FIGS. 16A-16E, FIGS. 17A-17C, FIGS. 18A-18G, FIGS. 19A-19E, FIGS.20A-20I, FIGS. 21A-21D, FIGS. 22A-22G, FIGS. 23A-23E, and 24A-24E.

Exemplary Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact, unless the contextclearly indicates otherwise.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch-screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch-screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display system112 is sometimes called a “touch screen” for convenience, and issometimes simply called a touch-sensitive display. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input or control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 163 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, firmware, or a combination thereof,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU(s) 120 and the peripheralsinterface 118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU(s) 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU(s) 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSDPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch-sensitive display system 112 and other input or control devices116, with peripherals interface 118. I/O subsystem 106 optionallyincludes display controller 156, optical sensor controller 158,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input or controldevices 116 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, joysticks, click wheels,and so forth. In some alternate embodiments, input controller(s) 160are, optionally, coupled with any (or none) of the following: akeyboard, infrared port, USB port, stylus, and/or a pointer device suchas a mouse. The one or more buttons (e.g., 208, FIG. 2) optionallyinclude an up/down button for volume control of speaker 111 and/ormicrophone 113. The one or more buttons optionally include a push button(e.g., 206, FIG. 2).

Touch-sensitive display system 112 provides an input interface and anoutput interface between the device and a user. Display controller 156receives and/or sends electrical signals from/to touch-sensitive displaysystem 112. Touch-sensitive display system 112 displays visual output tothe user. The visual output optionally includes graphics, text, icons,video, and any combination thereof (collectively termed “graphics”). Insome embodiments, some or all of the visual output corresponds to userinterface objects. As used herein, the term “affordance” is auser-interactive graphical user interface object (e.g., a graphical userinterface object that is configured to respond to inputs directed towardthe graphical user interface object). Examples of user-interactivegraphical user interface objects include, without limitation, a button,slider, icon, selectable menu item, switch, hyperlink, or other userinterface control.

Touch-sensitive display system 112 has a touch-sensitive surface, sensoror set of sensors that accepts input from the user based onhaptic/tactile contact. Touch-sensitive display system 112 and displaycontroller 156 (along with any associated modules and/or sets ofinstructions in memory 102) detect contact (and any movement or breakingof the contact) on touch-sensitive display system 112 and converts thedetected contact into interaction with user-interface objects (e.g., oneor more soft keys, icons, web pages or images) that are displayed ontouch-sensitive display system 112. In an example embodiment, a point ofcontact between touch-sensitive display system 112 and the usercorresponds to a finger of the user or a stylus.

Touch-sensitive display system 112 optionally uses LCD (liquid crystaldisplay) technology, LPD (light emitting polymer display) technology, orLED (light emitting diode) technology, although other displaytechnologies are used in other embodiments. Touch-sensitive displaysystem 112 and display controller 156 optionally detect contact and anymovement or breaking thereof using any of a plurality of touch sensingtechnologies now known or later developed, including but not limited tocapacitive, resistive, infrared, and surface acoustic wave technologies,as well as other proximity sensor arrays or other elements fordetermining one or more points of contact with touch-sensitive displaysystem 112. In an example embodiment, projected mutual capacitancesensing technology is used, such as that found in the iPhone®, iPodTouch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch-sensitive display system 112 optionally has a video resolution inexcess of 100 dpi. In some embodiments, the touch screen videoresolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater).The user optionally makes contact with touch-sensitive display system112 using any suitable object or appendage, such as a stylus, a finger,and so forth. In some embodiments, the user interface is designed towork with finger-based contacts and gestures, which can be less precisethan stylus-based input due to the larger area of contact of a finger onthe touch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch-sensitive displaysystem 112 or an extension of the touch-sensitive surface formed by thetouch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled with optical sensor controller158 in I/O subsystem 106. Optical sensor(s) 164 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 164 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor(s) 164 optionally capturestill images and/or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch-sensitive displaysystem 112 on the front of the device, so that the touch screen isenabled for use as a viewfinder for still and/or video imageacquisition. In some embodiments, another optical sensor is located onthe front of the device so that the user's image is obtained (e.g., forselfies, for videoconferencing while the user views the other videoconference participants on the touch screen, etc.).

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled withintensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor(s) 165 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a touch-sensitive surface). Contactintensity sensor(s) 165 receive contact intensity information (e.g.,pressure information or a proxy for pressure information) from theenvironment. In some embodiments, at least one contact intensity sensoris collocated with, or proximate to, a touch-sensitive surface (e.g.,touch-sensitive display system 112). In some embodiments, at least onecontact intensity sensor is located on the back of device 100, oppositetouch-screen display system 112 which is located on the front of device100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled with peripherals interface118. Alternately, proximity sensor 166 is coupled with input controller160 in I/O subsystem 106. In some embodiments, the proximity sensorturns off and disables touch-sensitive display system 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 163. FIG. 1A shows a tactile output generator coupled withhaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator(s) 163 optionally include one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Tactile output generator(s) 163 receive tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch-sensitive display system 112, which islocated on the front of device 100.

Device 100 optionally also includes one or more accelerometers 167,gyroscopes 168, and/or magnetometers 169 (e.g., as part of an inertialmeasurement unit (IMU)) for obtaining information concerning theposition (e.g., attitude) of the device. FIG. 1A shows sensors 167, 168,and 169 coupled with peripherals interface 118. Alternately, sensors167, 168, and 169 are, optionally, coupled with an input controller 160in I/O subsystem 106. In some embodiments, information is displayed onthe touch-screen display in a portrait view or a landscape view based onan analysis of data received from the one or more accelerometers. Device100 optionally includes a GPS (or GLONASS or other global navigationsystem) receiver (not shown) for obtaining information concerning thelocation of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,position module (or set of instructions) 131, graphics module (or set ofinstructions) 132, haptic feedback module (or set of instructions) 133,text input module (or set of instructions) 134, Global PositioningSystem (GPS) module (or set of instructions) 135, and applications (orsets of instructions) 136. Furthermore, in some embodiments, memory 102stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch-sensitive display system112; sensor state, including information obtained from the device'svarious sensors and other input or control devices 116; and locationand/or positional information concerning the device's location and/orattitude.

Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used in some iPhone®, iPod Touch®, and iPad® devicesfrom Apple Inc. of Cupertino, Calif. In some embodiments, the externalport is a Lightning connector that is the same as, or similar to and/orcompatible with the Lightning connector used in some iPhone®, iPodTouch®, and iPad® devices from Apple Inc. of Cupertino, Calif.

Contact/motion module 130 optionally detects contact withtouch-sensitive display system 112 (in conjunction with displaycontroller 156) and other touch-sensitive devices (e.g., a touchpad orphysical click wheel). Contact/motion module 130 includes softwarecomponents for performing various operations related to detection ofcontact (e.g., by a finger or by a stylus), such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningan intensity of the contact (e.g., the force or pressure of the contactor a substitute for the force or pressure of the contact), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, optionally includes determining speed (magnitude),velocity (magnitude and direction), and/or an acceleration (a change inmagnitude and/or direction) of the point of contact. These operationsare, optionally, applied to single contacts (e.g., one-finger contactsor stylus contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts and/or stylus contacts). In someembodiments, contact/motion module 130 and display controller 156 detectcontact on a touchpad.

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event. Similarly, tap,swipe, drag, and other gestures are optionally detected for a stylus bydetecting a particular contact pattern for the stylus.

In some embodiments, detecting a finger tap gesture depends on thelength of time between detecting the finger-down event and the finger-upevent, but is independent of the intensity of the finger contact betweendetecting the finger-down event and the finger-up event. In someembodiments, a tap gesture is detected in accordance with adetermination that the length of time between the finger-down event andthe finger-up event is less than a predetermined value (e.g., less than0.1, 0.2, 0.3, 0.4 or 0.5 seconds), independent of whether the intensityof the finger contact during the tap meets a given intensity threshold(greater than a nominal contact-detection intensity threshold), such asa light press or deep press intensity threshold. Thus, a finger tapgesture can satisfy particular input criteria that do not require thatthe characteristic intensity of a contact satisfy a given intensitythreshold in order for the particular input criteria to be met. Forclarity, the finger contact in a tap gesture typically needs to satisfya nominal contact-detection intensity threshold, below which the contactis not detected, in order for the finger-down event to be detected. Asimilar analysis applies to detecting a tap gesture by a stylus or othercontact. In cases where the device is capable of detecting a finger orstylus contact hovering over a touch sensitive surface, the nominalcontact-detection intensity threshold optionally does not correspond tophysical contact between the finger or stylus and the touch sensitivesurface.

The same concepts apply in an analogous manner to other types ofgestures. For example, a swipe gesture, a pinch gesture, a depinchgesture, and/or a long press gesture are optionally detected based onthe satisfaction of criteria that are either independent of intensitiesof contacts included in the gesture, or do not require that contact(s)that perform the gesture reach intensity thresholds in order to berecognized. For example, a swipe gesture is detected based on an amountof movement of one or more contacts; a pinch gesture is detected basedon movement of two or more contacts towards each other; a depinchgesture is detected based on movement of two or more contacts away fromeach other; and a long press gesture is detected based on a duration ofthe contact on the touch-sensitive surface with less than a thresholdamount of movement. As such, the statement that particular gesturerecognition criteria do not require that the intensity of the contact(s)meet a respective intensity threshold in order for the particulargesture recognition criteria to be met means that the particular gesturerecognition criteria are capable of being satisfied if the contact(s) inthe gesture do not reach the respective intensity threshold, and arealso capable of being satisfied in circumstances where one or more ofthe contacts in the gesture do reach or exceed the respective intensitythreshold. In some embodiments, a tap gesture is detected based on adetermination that the finger-down and finger-up event are detectedwithin a predefined time period, without regard to whether the contactis above or below the respective intensity threshold during thepredefined time period, and a swipe gesture is detected based on adetermination that the contact movement is greater than a predefinedmagnitude, even if the contact is above the respective intensitythreshold at the end of the contact movement. Even in implementationswhere detection of a gesture is influenced by the intensity of contactsperforming the gesture (e.g., the device detects a long press morequickly when the intensity of the contact is above an intensitythreshold or delays detection of a tap input when the intensity of thecontact is higher), the detection of those gestures does not requirethat the contacts reach a particular intensity threshold so long as thecriteria for recognizing the gesture can be met in circumstances wherethe contact does not reach the particular intensity threshold (e.g.,even if the amount of time that it takes to recognize the gesturechanges).

Contact intensity thresholds, duration thresholds, and movementthresholds are, in some circumstances, combined in a variety ofdifferent combinations in order to create heuristics for distinguishingtwo or more different gestures directed to the same input element orregion so that multiple different interactions with the same inputelement are enabled to provide a richer set of user interactions andresponses. The statement that a particular set of gesture recognitioncriteria do not require that the intensity of the contact(s) meet arespective intensity threshold in order for the particular gesturerecognition criteria to be met does not preclude the concurrentevaluation of other intensity-dependent gesture recognition criteria toidentify other gestures that do have a criteria that is met when agesture includes a contact with an intensity above the respectiveintensity threshold. For example, in some circumstances, first gesturerecognition criteria for a first gesture—which do not require that theintensity of the contact(s) meet a respective intensity threshold inorder for the first gesture recognition criteria to be met—are incompetition with second gesture recognition criteria for a secondgesture—which are dependent on the contact(s) reaching the respectiveintensity threshold. In such competitions, the gesture is, optionally,not recognized as meeting the first gesture recognition criteria for thefirst gesture if the second gesture recognition criteria for the secondgesture are met first. For example, if a contact reaches the respectiveintensity threshold before the contact moves by a predefined amount ofmovement, a deep press gesture is detected rather than a swipe gesture.Conversely, if the contact moves by the predefined amount of movementbefore the contact reaches the respective intensity threshold, a swipegesture is detected rather than a deep press gesture. Even in suchcircumstances, the first gesture recognition criteria for the firstgesture still do not require that the intensity of the contact(s) meet arespective intensity threshold in order for the first gesturerecognition criteria to be met because if the contact stayed below therespective intensity threshold until an end of the gesture (e.g., aswipe gesture with a contact that does not increase to an intensityabove the respective intensity threshold), the gesture would have beenrecognized by the first gesture recognition criteria as a swipe gesture.As such, particular gesture recognition criteria that do not requirethat the intensity of the contact(s) meet a respective intensitythreshold in order for the particular gesture recognition criteria to bemet will (A) in some circumstances ignore the intensity of the contactwith respect to the intensity threshold (e.g. for a tap gesture) and/or(B) in some circumstances still be dependent on the intensity of thecontact with respect to the intensity threshold in the sense that theparticular gesture recognition criteria (e.g., for a long press gesture)will fail if a competing set of intensity-dependent gesture recognitioncriteria (e.g., for a deep press gesture) recognize an input ascorresponding to an intensity-dependent gesture before the particulargesture recognition criteria recognize a gesture corresponding to theinput (e.g., for a long press gesture that is competing with a deeppress gesture for recognition).

Position module 131, in conjunction with accelerometers 167, gyroscopes168, and/or magnetometers 169, optionally detects positional informationconcerning the device, such as the device's attitude (roll, pitch,and/or yaw) in a particular frame of reference. Position module 130includes software components for performing various operations relatedto detecting the position of the device and detecting changes to theposition of the device. In some embodiments, position module 131 usesinformation received from a stylus being used with the device to detectpositional information concerning the stylus, such as detecting thepositional state of the stylus relative to the device and detectingchanges to the positional state of the stylus.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch-sensitive display system 112or other display, including components for changing the visual impact(e.g., brightness, transparency, saturation, contrast or other visualproperty) of graphics that are displayed. As used herein, the term“graphics” includes any object that can be displayed to a user,including without limitation text, web pages, icons (such asuser-interface objects including soft keys), digital images, videos,animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 163 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, contacts module 137 includes executable instructions tomanage an address book or contact list (e.g., stored in applicationinternal state 192 of contacts module 137 in memory 102 or memory 370),including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers and/or e-mail addresses to initiate and/or facilitatecommunications by telephone 138, video conference 139, e-mail 140, or IM141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, contact module 130, graphics module 132, and text input module 134,telephone module 138 includes executable instructions to enter asequence of characters corresponding to a telephone number, access oneor more telephone numbers in address book 137, modify a telephone numberthat has been entered, dial a respective telephone number, conduct aconversation and disconnect or hang up when the conversation iscompleted. As noted above, the wireless communication optionally usesany of a plurality of communications standards, protocols andtechnologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, optical sensor(s) 164, optical sensor controller 158, contactmodule 130, graphics module 132, text input module 134, contact list137, and telephone module 138, videoconferencing module 139 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, the instant messaging module 141 includesexecutable instructions to enter a sequence of characters correspondingto an instant message, to modify previously entered characters, totransmit a respective instant message (for example, using a ShortMessage Service (SMS) or Multimedia Message Service (MMS) protocol fortelephony-based instant messages or using XMPP, SIMPLE, Apple PushNotification Service (APNs) or IMPS for Internet-based instantmessages), to receive instant messages and to view received instantmessages. In some embodiments, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs,or IMPS).

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,text input module 134, GPS module 135, map module 154, and music playermodule 146, workout support module 142 includes executable instructionsto create workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (in sports devices and smartwatches); receive workout sensor data; calibrate sensors used to monitora workout; select and play music for a workout; and display, store andtransmit workout data.

In conjunction with touch-sensitive display system 112, displaycontroller 156, optical sensor(s) 164, optical sensor controller 158,contact module 130, graphics module 132, and image management module144, camera module 143 includes executable instructions to capture stillimages or video (including a video stream) and store them into memory102, modify characteristics of a still image or video, and/or delete astill image or video from memory 102.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, and camera module 143, image management module 144 includesexecutable instructions to arrange, modify (e.g., edit), or otherwisemanipulate, label, delete, present (e.g., in a digital slide show oralbum), and store still and/or video images.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, and text input module 134, browser module 147 includes executableinstructions to browse the Internet in accordance with userinstructions, including searching, linking to, receiving, and displayingweb pages or portions thereof, as well as attachments and other fileslinked to web pages.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, e-mail client module 140, and browser module147, calendar module 148 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, widget modules 149are mini-applications that are, optionally, downloaded and used by auser (e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, the widget creatormodule 150 includes executable instructions to create widgets (e.g.,turning a user-specified portion of a web page into a widget).

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, search module 151 includes executable instructions to searchfor text, music, sound, image, video, and/or other files in memory 102that match one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, and browser module 147, video andmusic player module 152 includes executable instructions that allow theuser to download and play back recorded music and other sound filesstored in one or more file formats, such as MP3 or AAC files, andexecutable instructions to display, present or otherwise play backvideos (e.g., on touch-sensitive display system 112, or on an externaldisplay connected wirelessly or via external port 124). In someembodiments, device 100 optionally includes the functionality of an MP3player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, notes module 153 includes executable instructions to createand manage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, GPS module 135, and browser module 147, mapmodule 154 includes executable instructions to receive, display, modify,and store maps and data associated with maps (e.g., driving directions;data on stores and other points of interest at or near a particularlocation; and other location-based data) in accordance with userinstructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesexecutable instructions that allow the user to access, browse, receive(e.g., by streaming and/or download), play back (e.g., on the touchscreen 112, or on an external display connected wirelessly or viaexternal port 124), send an e-mail with a link to a particular onlinevideo, and otherwise manage online videos in one or more file formats,such as H.264. In some embodiments, instant messaging module 141, ratherthan e-mail client module 140, is used to send a link to a particularonline video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 136, 137-155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay system 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display system 112, as part of amulti-touch gesture). Peripherals interface 118 transmits information itreceives from I/O subsystem 106 or a sensor, such as proximity sensor166, accelerometer(s) 167, gyroscope(s) 168, magnetometer(s) 169, and/ormicrophone 113 (through audio circuitry 110). Information thatperipheral interface 118 receives from I/O subsystem 106 includesinformation from touch-sensitive display system 112 or a touch-sensitivesurface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display system 112 displays more than one view.Views are made up of controls and other elements that a user can see onthe display.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay system 112, and lift-off of the touch (touch end). In someembodiments, the event also includes information for one or moreassociated event handlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display system 112, when a touch is detected ontouch-sensitive display system 112, event comparator 184 performs a hittest to determine which of the three user-interface objects isassociated with the touch (sub-event). If each displayed object isassociated with a respective event handler 190, the event comparatoruses the result of the hit test to determine which event handler 190should be activated. For example, event comparator 184 selects an eventhandler associated with the sub-event and the object triggering the hittest.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A) in accordancewith some embodiments. The touch screen optionally displays one or moregraphics within user interface (UI) 200. In this embodiment, as well asothers described below, a user is enabled to select one or more of thegraphics by making a gesture on the graphics, for example, with one ormore fingers 202 (not drawn to scale in the figure) or one or morestyluses 203 (not drawn to scale in the figure). In some embodiments,selection of one or more graphics occurs when the user breaks contactwith the one or more graphics. In some embodiments, the gestureoptionally includes one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some implementations orcircumstances, inadvertent contact with a graphic does not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon optionally does not select the corresponding application when thegesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on the touch-screen display.

In some embodiments, device 100 includes the touch-screen display, menubutton 204, push button 206 for powering the device on/off and lockingthe device, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In some embodiments, device 100 also accepts verbalinput for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch-sensitive display system 112 and/or one or more tactile outputgenerators 163 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch-screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 163 described above with reference to FIG. 1A), sensors 359(e.g., touch-sensitive, optical, contact intensity, proximity,acceleration, attitude, and/or magnetic sensors similar to sensors 112,164, 165, 166, 167, 168, and 169 described above with reference to FIG.1A). Memory 370 includes high-speed random access memory, such as DRAM,SRAM, DDR RAM or other random access solid state memory devices; andoptionally includes non-volatile memory, such as one or more magneticdisk storage devices, optical disk storage devices, flash memorydevices, or other non-volatile solid state storage devices. Memory 370optionally includes one or more storage devices remotely located fromCPU(s) 310. In some embodiments, memory 370 stores programs, modules,and data structures analogous to the programs, modules, and datastructures stored in memory 102 of portable multifunction device 100(FIG. 1A), or a subset thereof. Furthermore, memory 370 optionallystores additional programs, modules, and data structures not present inmemory 102 of portable multifunction device 100. For example, memory 370of device 300 optionally stores drawing module 380, presentation module382, word processing module 384, website creation module 386, diskauthoring module 388, and/or spreadsheet module 390, while memory 102 ofportable multifunction device 100 (FIG. 1A) optionally does not storethese modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

FIG. 4 is a block diagram of an exemplary electronic stylus 203 inaccordance with some embodiments. Electronic stylus 203 is sometimessimply called a stylus. Stylus 203 includes memory 402 (which optionallyincludes one or more computer readable storage mediums), memorycontroller 422, one or more processing units (CPUs) 420, peripheralsinterface 418, RF circuitry 408, input/output (I/O) subsystem 406, andother input or control devices 416. Stylus 203 optionally includesexternal port 424 and one or more optical sensors 464. Stylus 203optionally includes one or more intensity sensors 465 for detectingintensity of contacts of stylus 203 on device 100 (e.g., when stylus 203is used with a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100) or on other surfaces (e.g., a desk surface).Stylus 203 optionally includes one or more tactile output generators 463for generating tactile outputs on stylus 203. These componentsoptionally communicate over one or more communication buses or signallines 403.

In some embodiments, the term “tactile output,” discussed above, refersto physical displacement of an accessory (e.g., stylus 203) of a device(e.g., device 100) relative to a previous position of the accessory,physical displacement of a component of an accessory relative to anothercomponent of the accessory, or displacement of the component relative toa center of mass of the accessory that will be detected by a user withthe user's sense of touch. For example, in situations where theaccessory or the component of the accessory is in contact with a surfaceof a user that is sensitive to touch (e.g., a finger, palm, or otherpart of a user's hand), the tactile output generated by the physicaldisplacement will be interpreted by the user as a tactile sensationcorresponding to a perceived change in physical characteristics of theaccessory or the component of the accessory. For example, movement of acomponent (e.g., the housing of stylus 203) is, optionally, interpretedby the user as a “click” of a physical actuator button. In some cases, auser will feel a tactile sensation such as a “click” even when there isno movement of a physical actuator button associated with the stylusthat is physically pressed (e.g., displaced) by the user's movements.While such interpretations of touch by a user will be subject to theindividualized sensory perceptions of the user, there are many sensoryperceptions of touch that are common to a large majority of users. Thus,when a tactile output is described as corresponding to a particularsensory perception of a user (e.g., a “click,”), unless otherwisestated, the generated tactile output corresponds to physicaldisplacement of the device or a component thereof that will generate thedescribed sensory perception for a typical (or average) user.

It should be appreciated that stylus 203 is only one example of anelectronic stylus, and that stylus 203 optionally has more or fewercomponents than shown, optionally combines two or more components, oroptionally has a different configuration or arrangement of thecomponents. The various components shown in FIG. 4 are implemented inhardware, software, firmware, or a combination thereof, including one ormore signal processing and/or application specific integrated circuits.

Memory 402 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or more flashmemory devices, or other non-volatile solid-state memory devices. Accessto memory 402 by other components of stylus 203, such as CPU(s) 420 andthe peripherals interface 418, is, optionally, controlled by memorycontroller 422.

Peripherals interface 418 can be used to couple input and outputperipherals of the stylus to CPU(s) 420 and memory 402. The one or moreprocessors 420 run or execute various software programs and/or sets ofinstructions stored in memory 402 to perform various functions forstylus 203 and to process data.

In some embodiments, peripherals interface 418, CPU(s) 420, and memorycontroller 422 are, optionally, implemented on a single chip, such aschip 404. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 408 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 408 converts electricalsignals to/from electromagnetic signals and communicates with device 100or 300, communications networks, and/or other communications devices viathe electromagnetic signals. RF circuitry 408 optionally includeswell-known circuitry for performing these functions, including but notlimited to an antenna system, an RF transceiver, one or more amplifiers,a tuner, one or more oscillators, a digital signal processor, a CODECchipset, a subscriber identity module (SIM) card, memory, and so forth.RF circuitry 408 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

I/O subsystem 406 couples input/output peripherals on stylus 203, suchas other input or control devices 416, with peripherals interface 418.I/O subsystem 406 optionally includes optical sensor controller 458,intensity sensor controller 459, haptic feedback controller 461, and oneor more input controllers 460 for other input or control devices. Theone or more input controllers 460 receive/send electrical signalsfrom/to other input or control devices 416. The other input or controldevices 416 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, click wheels, and soforth. In some alternate embodiments, input controller(s) 460 are,optionally, coupled with any (or none) of the following: an infraredport and/or a USB port.

Stylus 203 also includes power system 462 for powering the variouscomponents. Power system 462 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices and/or portableaccessories.

Stylus 203 optionally also includes one or more optical sensors 464.FIG. 4 shows an optical sensor coupled with optical sensor controller458 in I/O subsystem 406. Optical sensor(s) 464 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 464 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image.

Stylus 203 optionally also includes one or more contact intensitysensors 465. FIG. 4 shows a contact intensity sensor coupled withintensity sensor controller 459 in I/O subsystem 406. Contact intensitysensor(s) 465 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a surface). Contact intensitysensor(s) 465 receive contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a tip of stylus 203.

Stylus 203 optionally also includes one or more proximity sensors 466.FIG. 4 shows proximity sensor 466 coupled with peripherals interface418. Alternately, proximity sensor 466 is coupled with input controller460 in I/O subsystem 406. In some embodiments, the proximity sensordetermines proximity of stylus 203 to an electronic device (e.g., device100).

Stylus 203 optionally also includes one or more tactile outputgenerators 463. FIG. 4 shows a tactile output generator coupled withhaptic feedback controller 461 in I/O subsystem 406. Tactile outputgenerator(s) 463 optionally include one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Tactile output generator(s) 463 receive tactile feedbackgeneration instructions from haptic feedback module 433 and generatestactile outputs on stylus 203 that are capable of being sensed by a userof stylus 203. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a length (e.g., a body ora housing) of stylus 203 and, optionally, generates a tactile output bymoving stylus 203 vertically (e.g., in a direction parallel to thelength of stylus 203) or laterally (e.g., in a direction normal to thelength of stylus 203).

Stylus 203 optionally also includes one or more accelerometers 467,gyroscopes 468, and/or magnetometers 470 (e.g., as part of an inertialmeasurement unit (IMU)) for obtaining information concerning thelocation and positional state of stylus 203. FIG. 4 shows sensors 467,469, and 470 coupled with peripherals interface 418. Alternately,sensors 467, 469, and 470 are, optionally, coupled with an inputcontroller 460 in I/O subsystem 406. Stylus 203 optionally includes aGPS (or GLONASS or other global navigation system) receiver (not shown)for obtaining information concerning the location of stylus 203.

In some embodiments, the software components stored in memory 402include operating system 426, communication module (or set ofinstructions) 428, contact/motion module (or set of instructions) 430,position module (or set of instructions) 431, and Global PositioningSystem (GPS) module (or set of instructions) 435. Furthermore, in someembodiments, memory 402 stores device/global internal state 457, asshown in FIG. 4. Device/global internal state 457 includes one or moreof: sensor state, including information obtained from the stylus'svarious sensors and other input or control devices 416; positionalstate, including information regarding the stylus's position (e.g.,position, orientation, tilt, roll and/or distance, as shown in FIGS. 5Aand 5B) relative to a device (e.g., device 100); and locationinformation concerning the stylus's location (e.g., determined by GPSmodule 435).

Operating system 426 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, power management, etc.)and facilitates communication between various hardware and softwarecomponents.

Communication module 428 optionally facilitates communication with otherdevices over one or more external ports 424 and also includes varioussoftware components for handling data received by RF circuitry 408and/or external port 424. External port 424 (e.g., Universal Serial Bus(USB), FIREWIRE, etc.) is adapted for coupling directly to other devicesor indirectly over a network (e.g., the Internet, wireless LAN, etc.).In some embodiments, the external port is a Lightning connector that isthe same as, or similar to and/or compatible with the Lightningconnector used in some iPhone®, iPod Touch®, and iPad® devices fromApple Inc. of Cupertino, Calif.

Contact/motion module 430 optionally detects contact with stylus 203 andother touch-sensitive devices of stylus 203 (e.g., buttons or othertouch-sensitive components of stylus 203). Contact/motion module 430includes software components for performing various operations relatedto detection of contact (e.g., detection of a tip of the stylus with atouch-sensitive display, such as touch screen 112 of device 100, or withanother surface, such as a desk surface), such as determining if contacthas occurred (e.g., detecting a touch-down event), determining anintensity of the contact (e.g., the force or pressure of the contact ora substitute for the force or pressure of the contact), determining ifthere is movement of the contact and tracking the movement (e.g., acrosstouch screen 112 of device 100), and determining if the contact hasceased (e.g., detecting a lift-off event or a break in contact). In someembodiments, contact/motion module 430 receives contact data from I/Osubsystem 406. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. As noted above, in some embodiments, one or more of theseoperations related to detection of contact are performed by the deviceusing contact/motion module 130 (in addition to or in place of thestylus using contact/motion module 430).

Contact/motion module 430 optionally detects a gesture input by stylus203. Different gestures with stylus 203 have different contact patterns(e.g., different motions, timings, and/or intensities of detectedcontacts). Thus, a gesture is, optionally, detected by detecting aparticular contact pattern. For example, detecting a single tap gestureincludes detecting a touch-down event followed by detecting a lift-offevent at the same position (or substantially the same position) as thetouch-down event (e.g., at the position of an icon). As another example,detecting a swipe gesture includes detecting a touch-down event followedby detecting one or more stylus-dragging events, and subsequentlyfollowed by detecting a lift-off event. As noted above, in someembodiments, gesture detection is performed by the device usingcontact/motion module 130 (in addition to or in place of the stylususing contact/motion module 430).

Position module 431, in conjunction with accelerometers 467, gyroscopes468, and/or magnetometers 469, optionally detects positional informationconcerning the stylus, such as the stylus's attitude (roll, pitch,and/or yaw) in a particular frame of reference. Position module 431, inconjunction with accelerometers 467, gyroscopes 468, and/ormagnetometers 469, optionally detects stylus movement gestures, such asflicks, taps, and rolls of the stylus. Position module 431 includessoftware components for performing various operations related todetecting the position of the stylus and detecting changes to theposition of the stylus in a particular frame of reference. In someembodiments, position module 431 detects the positional state of thestylus relative to the device and detects changes to the positionalstate of the stylus relative to the device. As noted above, in someembodiments, device 100 or 300 determines the positional state of thestylus relative to the device and changes to the positional state of thestylus using position module 131 (in addition to or in place of thestylus using position module 431).

Haptic feedback module 433 includes various software components forgenerating instructions used by tactile output generator(s) 463 toproduce tactile outputs at one or more locations on stylus 203 inresponse to user interactions with stylus 203.

GPS module 435 determines the location of the stylus and provides thisinformation for use in various applications (e.g., to applications thatprovide location-based services such as an application to find missingdevices and/or accessories).

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 402 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 402 optionally stores additionalmodules and data structures not described above.

FIGS. 5A-5B illustrate a positional state of stylus 203 relative to atouch-sensitive surface (e.g., touch screen 112 of device 100) inaccordance with some embodiments. In some embodiments, the positionalstate of stylus 203 corresponds to (or indicates): a position of aprojection of a tip (or other representative portion) of the stylus onthe touch-sensitive surface (e.g., (x,y) position 504, FIG. 5A), anorientation of the stylus relative to the touch-sensitive surface (e.g.,orientation 506, FIG. 5A), a tilt of the stylus relative to thetouch-sensitive surface (e.g., tilt 512, FIG. 5B), and/or a distance ofthe stylus relative to the touch-sensitive surface (e.g., distance 514,FIG. 5B). In some embodiments, the positional state of stylus 203corresponds to (or indicates) a pitch, yaw, and/or roll of the stylus(e.g., an attitude of the stylus relative to a particular frame ofreference, such as a touch-sensitive surface (e.g., touch screen 112) orthe ground). In some embodiments, the positional state includes a set ofpositional parameters (e.g., one or more positional parameters). In someembodiments, the positional state is detected in accordance with one ormore measurements from stylus 203 that are sent to an electronic device(e.g., device 100). For example, the stylus measures the tilt (e.g.,tilt 512, FIG. 5B) and/or the orientation (e.g., orientation 506, FIG.5A) of the stylus and sends the measurement to device 100. In someembodiments, the positional state is detected in accordance with rawoutput, from one or more electrodes in the stylus, that is sensed by atouch-sensitive surface (e.g., touch screen 112 of device 100) insteadof, or in combination with positional state detected in accordance withone or more measurements from stylus 203. For example, thetouch-sensitive surface receives raw output from one or more electrodesin the stylus and calculates the tilt and/or the orientation of thestylus based on the raw output (optionally, in conjunction withpositional state information provided by the stylus based on sensormeasurements generated by the stylus).

FIG. 5A illustrates stylus 203 relative to a touch-sensitive surface(e.g., touch screen 112 of device 100) from a viewpoint directly abovethe touch-sensitive surface, in accordance with some embodiments. InFIG. 5A, z-axis 594 points out of the page (i.e., in a direction normalto a plane of touch screen 112), x-axis 590 is parallel to a first edge(e.g., a length) of touch screen 112, y-axis 592 is parallel to a secondedge (e.g., a width) of touch screen 112, and y-axis 592 isperpendicular to x-axis 590.

FIG. 5A illustrates the tip of stylus 203 at (x,y) position 504. In someembodiments, the tip of stylus 203 is a terminus of the stylusconfigured for determining proximity of the stylus to a touch-sensitivesurface (e.g., touch screen 112). In some embodiments, the projection ofthe tip of the stylus on the touch-sensitive surface is an orthogonalprojection. In other words, the projection of the tip of the stylus onthe touch-sensitive surface is a point at the end of a line from thestylus tip to the touch-sensitive surface that is normal to a surface ofthe touch-sensitive surface (e.g., (x,y) position 504 at which the tipof the stylus would touch the touch-sensitive surface if the stylus weremoved directly along a path normal to the touch-sensitive surface). Insome embodiments, the (x,y) position at the lower left corner of touchscreen 112 is position (0,0) (e.g., (0,0) position 502) and other (x,y)positions on touch screen 112 are relative to the lower left corner oftouch screen 112. Alternatively, in some embodiments, the (0,0) positionis located at another position of touch screen 112 (e.g., in the centerof touch screen 112) and other (x,y) positions are relative to the (0,0)position of touch screen 112.

Further, FIG. 5A illustrates stylus 203 with orientation 506. In someembodiments, orientation 506 is an orientation of a projection of stylus203 onto touch screen 112 (e.g., an orthogonal projection of a length ofstylus 203 or a line corresponding to the line between the projection oftwo different points of stylus 203 onto touch screen 112). In someembodiments, orientation 506 is relative to at least one axis in a planeparallel to touch screen 112. In some embodiments, orientation 506 isrelative to a single axis in a plane parallel to touch screen 112 (e.g.,axis 508, with a clockwise rotation angle from axis 508 ranging from 0degrees to 360 degrees, as shown in FIG. 5A). Alternatively, in someembodiments, orientation 506 is relative to a pair of axes in a planeparallel to touch screen 112 (e.g., x-axis 590 and y-axis 592, as shownin FIG. 5A, or a pair of axes associated with an application displayedon touch screen 112).

In some embodiments, an indication (e.g., indication 516) is displayedon a touch-sensitive display (e.g., touch screen 112 of device 100). Insome embodiments, indication 516 shows where the stylus will touch (ormark) the touch-sensitive display before the stylus touches thetouch-sensitive display. In some embodiments, indication 516 is aportion of a mark that is being drawn on the touch-sensitive display. Insome embodiments, indication 516 is separate from a mark that is beingdrawn on the touch-sensitive display and corresponds to a virtual “pentip” or other element that indicates where a mark will be drawn on thetouch-sensitive display.

In some embodiments, indication 516 is displayed in accordance with thepositional state of stylus 203. For example, in some circumstances,indication 516 is displaced from (x,y) position 504 (as shown in FIGS.5A and 5B), and in other circumstances, indication 516 is not displacedfrom (x,y) position 504 (e.g., indication 516 is displayed at or near(x,y) position 504 when tilt 512 is zero degrees). In some embodiments,indication 516 is displayed, in accordance with the positional state ofthe stylus, with varying color, size (or radius or area), opacity,and/or other characteristics. In some embodiments, the displayedindication accounts for thickness of a glass layer on thetouch-sensitive display, so as to carry through the indication “onto thepixels” of the touch-sensitive display, rather than displaying theindication “on the glass” that covers the pixels. As used herein,“indication” may also be used to refer to a position that is not visibleon the touch-screen when describing the exemplary user interfaces.

FIG. 5B illustrates stylus 203 relative to a touch-sensitive surface(e.g., touch screen 112 of device 100) from a side viewpoint of thetouch-sensitive surface, in accordance with some embodiments. In FIG.5B, z-axis 594 points in a direction normal to the plane of touch screen112, x-axis 590 is parallel to a first edge (e.g., a length) of touchscreen 112, y-axis 592 is parallel to a second edge (e.g., a width) oftouch screen 112, and y-axis 592 is perpendicular to x-axis 590.

FIG. 5B illustrates stylus 203 with tilt 512. In some embodiments, tilt512 is an angle relative to a normal (e.g., normal 510) to a surface ofthe touch-sensitive surface (also called simply the normal to thetouch-sensitive surface). As shown in FIG. 5B, tilt 512 is zero when thestylus is perpendicular/normal to the touch-sensitive surface (e.g.,when stylus 203 is parallel to normal 510) and the tilt increases as thestylus is tilted closer to being parallel to the touch-sensitivesurface.

Further, FIG. 5B illustrates distance 514 of stylus 203 relative to thetouch-sensitive surface. In some embodiments, distance 514 is thedistance from the tip of stylus 203 to the touch-sensitive surface, in adirection normal to the touch-sensitive surface. For example, in FIG.5B, distance 514 is the distance from the tip of stylus 203 to (x,y)position 504.

Although the terms, “x-axis,” “y-axis,” and “z-axis,” are used herein toillustrate certain directions in particular figures, it will beunderstood that these terms do not refer to absolute directions. Inother words, an “x-axis” could be any respective axis, and a “y-axis”could be a particular axis that is distinct from the x-axis. Typically,the x-axis is perpendicular to the y-axis. Similarly, a “z-axis” isdistinct from the “x-axis” and the “y-axis,” and is typicallyperpendicular to both the “x-axis” and the “y-axis.”

Further, FIG. 5B illustrates roll 518, a rotation about the length (longaxis) of stylus 203.

Attention is now directed towards embodiments of user interfaces (“UI”)that are, optionally, implemented on portable multifunction device 100.

FIG. 6A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 600 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 602 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 604;    -   Bluetooth indicator 605;    -   Battery status indicator 606;    -   Tray 608 with icons for frequently used applications, such as:        -   Icon 616 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 614 of the number of missed            calls or voicemail messages;        -   Icon 618 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 610 of the number of unread            e-mails;        -   Icon 620 for browser module 147, labeled “Browser;” and        -   Icon 622 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 624 for IM module 141, labeled “Text;”        -   Icon 626 for calendar module 148, labeled “Calendar;”        -   Icon 628 for image management module 144, labeled “Photos;”        -   Icon 630 for camera module 143, labeled “Camera;”        -   Icon 632 for online video module 155, labeled “Online            Video;”        -   Icon 634 for stocks widget 149-2, labeled “Stocks;”        -   Icon 636 for map module 154, labeled “Map;”        -   Icon 638 for weather widget 149-1, labeled “Weather;”        -   Icon 640 for alarm clock widget 169-6, labeled “Clock;”        -   Icon 642 for workout support module 142, labeled “Workout            Support;”        -   Icon 644 for notes module 153, labeled “Notes;” and        -   Icon 646 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 6A aremerely exemplary. For example, in some embodiments, icon 622 for videoand music player module 152 is labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 6B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 651 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 650. Device300 also, optionally, includes one or more contact intensity sensors(e.g., one or more of sensors 359) for detecting intensity of contactson touch-sensitive surface 651 and/or one or more tactile outputgenerators 359 for generating tactile outputs for a user of device 300.

FIG. 6B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 651 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 650. In someembodiments, the touch-sensitive surface (e.g., 651 in FIG. 6B) has aprimary-axis (e.g., 652 in FIG. 6B) that corresponds to a primary-axis(e.g., 653 in FIG. 6B) on the display (e.g., 650). In accordance withthese embodiments, the device detects contacts (e.g., 660 and 662 inFIG. 6B) with the touch-sensitive surface 651 at locations thatcorrespond to respective locations on the display (e.g., in FIG. 6B, 660corresponds to 668 and 662 corresponds to 670). In this way, user inputs(e.g., contacts 660 and 662, and movements thereof) detected by thedevice on the touch-sensitive surface (e.g., 651 in FIG. 6B) are used bythe device to manipulate the user interface on the display (e.g., 650 inFIG. 6B) of the multifunction device when the touch-sensitive surface isseparate from the display. Some of the examples that follow will begiven with reference to a device that detects inputs on atouch-sensitive surface that is separate from the display, as shown inFIG. 6B. Some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch sensitive surfaceand the display are combined). It should be understood that similarmethods are, optionally, used for other user interfaces describedherein.

Additionally, while some of the following examples are given primarilywith reference to finger inputs (e.g., finger contacts, finger tapgestures, finger press gestures, and finger swipe gestures, etc.), itshould be understood that, in some embodiments, one or more of thefinger inputs are replaced with input from another input device (e.g., amouse based input or a stylus based input). For example, a swipe gestureis, optionally, replaced with a mouse click (e.g., instead of a contact)followed by movement of the cursor along the path of the swipe (e.g.,instead of movement of the contact). As another example, a tap gestureis, optionally, replaced with a mouse click while the cursor is locatedover the location of the tap gesture (e.g., instead of detection of thecontact followed by ceasing to detect the contact). Similarly, whenmultiple user inputs are simultaneously detected, it should beunderstood that multiple computer mice are, optionally, usedsimultaneously, or a mouse and finger contacts are, optionally, usedsimultaneously.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 651 in FIG. 6B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or the touch screenin FIG. 6A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device). Asused herein, a “focus selector” may be a visible “indication” or aninvisible “indication” of a hovering input object (e.g., a finger orstylus).

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact or a styluscontact) on the touch-sensitive surface, or to a substitute (proxy) forthe force or pressure of a contact on the touch-sensitive surface. Theintensity of a contact has a range of values that includes at least fourdistinct values and more typically includes hundreds of distinct values(e.g., at least 256). Intensity of a contact is, optionally, determined(or measured) using various approaches and various sensors orcombinations of sensors. For example, one or more force sensorsunderneath or adjacent to the touch-sensitive surface are, optionally,used to measure force at various points on the touch-sensitive surface.In some implementations, force measurements from multiple force sensorsare combined (e.g., a weighted average or a sum) to determine anestimated force of a contact. Similarly, a pressure-sensitive tip of astylus is, optionally, used to determine a pressure of the stylus on thetouch-sensitive surface. Alternatively, the size of the contact areadetected on the touch-sensitive surface and/or changes thereto, thecapacitance of the touch-sensitive surface proximate to the contactand/or changes thereto, and/or the resistance of the touch-sensitivesurface proximate to the contact and/or changes thereto are, optionally,used as a substitute for the force or pressure of the contact on thetouch-sensitive surface. In some implementations, the substitutemeasurements for contact force or pressure are used directly todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is described in units corresponding to thesubstitute measurements). In some implementations, the substitutemeasurements for contact force or pressure are converted to an estimatedforce or pressure and the estimated force or pressure is used todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is a pressure threshold measured in units ofpressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be readily accessible by the user on a reduced-size devicewith limited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

In some embodiments, contact/motion module 130 and/or 430 uses a set ofone or more intensity thresholds to determine whether an operation hasbeen performed by a user (e.g., to determine whether a user has“clicked” on an icon). In some embodiments, at least a subset of theintensity thresholds are determined in accordance with softwareparameters (e.g., the intensity thresholds are not determined by theactivation thresholds of particular physical actuators and can beadjusted without changing the physical hardware of device 100). Forexample, a mouse “click” threshold of a trackpad or touch-screen displaycan be set to any of a large range of predefined thresholds valueswithout changing the trackpad or touch-screen display hardware.Additionally, in some embodiments, a user of the device is provided withsoftware settings for adjusting one or more of the set of intensitythresholds (e.g., by adjusting individual intensity thresholds and/or byadjusting a plurality of intensity thresholds at once with asystem-level click “intensity” parameter).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second intensity threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more intensity thresholds is used to determine whether or not toperform one or more operations (e.g., whether to perform a respectiveoption or forgo performing the respective operation) rather than beingused to determine whether to perform a first operation or a secondoperation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location (e.g.,a drag gesture), at which point the intensity of the contact increases.In this example, the characteristic intensity of the contact at the endlocation may be based on only a portion of the continuous swipe contact,and not the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmmay be applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The user interface figures (e.g., FIGS. 7A-7AU) described belowoptionally include various intensity diagrams that show the currentintensity of the contact on the touch-sensitive surface relative to oneor more intensity thresholds (e.g., a contact detection intensitythreshold IT₀, a light press intensity threshold IT_(L), a deep pressintensity threshold IT_(D), and/or one or more other intensitythresholds). This intensity diagram is typically not part of thedisplayed user interface, but is provided to aid in the interpretationof the figures. In some embodiments, the light press intensity thresholdcorresponds to an intensity at which the device will perform operationstypically associated with clicking a button of a physical mouse or atrackpad. In some embodiments, the deep press intensity thresholdcorresponds to an intensity at which the device will perform operationsthat are different from operations typically associated with clicking abutton of a physical mouse or a trackpad. In some embodiments, when acontact is detected with a characteristic intensity below the lightpress intensity threshold (e.g., and above a nominal contact-detectionintensity threshold IT₀ below which the contact is no longer detected),the device will move a focus selector in accordance with movement of thecontact on the touch-sensitive surface without performing an operationassociated with the light press intensity threshold or the deep pressintensity threshold. Generally, unless otherwise stated, these intensitythresholds are consistent between different sets of user interfacefigures.

In some embodiments, the response of the device to inputs detected bythe device depends on criteria based on the contact intensity during theinput. For example, for some “light press” inputs, the intensity of acontact exceeding a first intensity threshold during the input triggersa first response. In some embodiments, the response of the device toinputs detected by the device depends on criteria that include both thecontact intensity during the input and time-based criteria. For example,for some “deep press” inputs, the intensity of a contact exceeding asecond intensity threshold during the input, greater than the firstintensity threshold for a light press, triggers a second response onlyif a delay time has elapsed between meeting the first intensitythreshold and meeting the second intensity threshold. This delay time istypically less than 200 ms in duration (e.g., 40, 100, or 120 ms,depending on the magnitude of the second intensity threshold, with thedelay time increasing as the second intensity threshold increases). Thisdelay time helps to avoid accidental deep press inputs. As anotherexample, for some “deep press” inputs, there is a reduced-sensitivitytime period that occurs after the time at which the first intensitythreshold is met. During the reduced-sensitivity time period, the secondintensity threshold is increased. This temporary increase in the secondintensity threshold also helps to avoid accidental deep press inputs.For other deep press inputs, the response to detection of a deep pressinput does not depend on time-based criteria.

In some embodiments, one or more of the input intensity thresholdsand/or the corresponding outputs vary based on one or more factors, suchas user settings, contact motion, input timing, application running,rate at which the intensity is applied, number of concurrent inputs,user history, environmental factors (e.g., ambient noise), focusselector position, and the like. Exemplary factors are described in U.S.patent application Ser. Nos. 14/399,606 and 14/624,296, which areincorporated by reference herein in their entireties.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold IT_(L) to an intensity betweenthe light press intensity threshold IT_(L) and the deep press intensitythreshold IT_(D) is sometimes referred to as a “light press” input. Anincrease of characteristic intensity of the contact from an intensitybelow the deep press intensity threshold IT_(D) to an intensity abovethe deep press intensity threshold IT_(D) is sometimes referred to as a“deep press” input. An increase of characteristic intensity of thecontact from an intensity below the contact-detection intensitythreshold IT₀ to an intensity between the contact-detection intensitythreshold IT₀ and the light press intensity threshold IT_(L) issometimes referred to as detecting the contact on the touch-surface. Adecrease of characteristic intensity of the contact from an intensityabove the contact-detection intensity threshold IT₀ to an intensitybelow the contact-detection intensity threshold IT₀ is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, IT₀ is zero. In some embodiments, IT₀ is greaterthan zero. In some illustrations, a shaded circle or oval is used torepresent intensity of a contact on the touch-sensitive surface. In someillustrations, a circle or oval without shading is used represent arespective contact on the touch-sensitive surface without specifying theintensity of the respective contact.

In some embodiments, described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., the respective operation is performed on a“down stroke” of the respective press input). In some embodiments, thepress input includes an increase in intensity of the respective contactabove the press-input intensity threshold and a subsequent decrease inintensity of the contact below the press-input intensity threshold, andthe respective operation is performed in response to detecting thesubsequent decrease in intensity of the respective contact below thepress-input threshold (e.g., the respective operation is performed on an“up stroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., the respective operationis performed on an “up stroke” of the respective press input).Similarly, in some embodiments, the press input is detected only whenthe device detects an increase in intensity of the contact from anintensity at or below the hysteresis intensity threshold to an intensityat or above the press-input intensity threshold and, optionally, asubsequent decrease in intensity of the contact to an intensity at orbelow the hysteresis intensity, and the respective operation isperformed in response to detecting the press input (e.g., the increasein intensity of the contact or the decrease in intensity of the contact,depending on the circumstances).

For ease of explanation, the description of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting: an increase in intensityof a contact above the press-input intensity threshold, an increase inintensity of a contact from an intensity below the hysteresis intensitythreshold to an intensity above the press-input intensity threshold, adecrease in intensity of the contact below the press-input intensitythreshold, or a decrease in intensity of the contact below thehysteresis intensity threshold corresponding to the press-inputintensity threshold. Additionally, in examples where an operation isdescribed as being performed in response to detecting a decrease inintensity of a contact below the press-input intensity threshold, theoperation is, optionally, performed in response to detecting a decreasein intensity of the contact below a hysteresis intensity thresholdcorresponding to, and lower than, the press-input intensity threshold.As described above, in some embodiments, the triggering of theseresponses also depends on time-based criteria being met (e.g., a delaytime has elapsed between a first intensity threshold being met and asecond intensity threshold being met).

User Interfaces and Associated Processes

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronicdevice, such as portable multifunction device 100 or device 300, with adisplay, a touch-sensitive surface, and (optionally) one or more sensorsto detect intensities of contacts with the touch-sensitive surface.

FIGS. 7A-7AU, FIGS. 8A-8V, FIGS. 9A-9O, FIGS. 10A-10Y, FIGS. 11A-11J,FIGS. 12A-12R, FIGS. 13A-13N, and FIGS. 14A-14L illustrate exemplaryuser interfaces for interacting with a user interface object throughproximity-based inputs and contact-based inputs by an input object inaccordance with some embodiments. The user interfaces in these figuresare used to illustrate the processes described below, including theprocesses in FIGS. 15A-15C, FIGS. 16A-16E, FIGS. 17A-17C, FIGS. 18A-18G,FIGS. 19A-19E, FIGS. 20A-20I, FIGS. 21A-21D, FIGS. 22A-22G, FIGS.23A-23E, and 24A-24E. Although some of the examples which follow will begiven with reference to inputs on a touch-sensitive surface 651 that isseparate from the display 650, in some embodiments, the device detectsinputs on a touch-screen display (where the touch-sensitive surface andthe display are combined), as shown in FIG. 6A. Although some of theexamples which follow will be given with reference to inputs on atouch-screen display (where the touch-sensitive surface and the displayare combined), in some embodiments, the device detects inputs on atouch-sensitive surface 651 that is separate from the display 650, asshown in FIG. 6B.

FIGS. 7A-7U illustrate a process for interacting with a user interfaceobject (e.g., including picking up, moving, and dropping off the userinterface object) through proximity-based inputs and contact-basedinputs by an input object (e.g., a finger or a stylus, such as stylus203). Although this example is given with reference to inputs providedby stylus 203, in some embodiments, the device detects inputs providedby other types of input objects, such as a finger, a wand, a handheldcontroller, etc., to perform the operations illustrated below.

The input parameters of an input provided by the input object (anddetected by the electronic device (e.g., device 100)) include a hoverproximity parameter that is (or is calculated based on) a distance(e.g., distance 514) between a predetermined portion of the input object(e.g., the tip of the finger, or the tip of the stylus) and atouch-sensitive surface (e.g., touch-screen 112 or touch-sensitivesurface 651). In some embodiments, the input parameters include thelateral position (e.g., (x, y) position 504) of the input object (e.g.,finger or stylus 203) relative to the touch-sensitive surface. In someembodiments, the input parameters include the three-dimensionalpositional state and movement of the input object, e.g., as describedwith respect to FIGS. 5A and 5B. In some embodiments, when the inputobject is in contact with the touch-sensitive surface, the inputparameters include a characteristic intensity and position of a contactby the input object (e.g., the tip of the finger or stylus) with thetouch-sensitive surface.

In FIG. 7A, user interface 702 is displayed on display 650. Userinterface 702 includes a number of user interface objects (e.g.,represented by a row and a column of circles), including user interfaceobject 704 (e.g., an application launch icon, a button, etc.). When thetip of stylus 203 is held at a distance (e.g., distance 514) that ismore than the threshold hover distance away from the touch-sensitivesurface, the device optionally does not display any visual indicator orfocus selector that corresponds to stylus 203 on the display.

FIG. 7B illustrate that, when the tip of stylus 203 is moved toward thetouch-sensitive surface and is held within the threshold hover distanceof the touch-sensitive surface, the device optionally displays a visualindicator (e.g., indicator 706 (e.g., pointing hand 706-a)). Indicator706 is displayed at a location in user interface 702 that corresponds toa position (e.g., position 701) on the touch-sensitive surface that isdetermined based on the lateral position (e.g., (x,y) position 504) ofstylus 203 and, optionally, the vertical position and/or positionalstate of stylus 203. As shown in FIG. 7B, when the tip of stylus 203 isabove touch-sensitive surface 651 and not in contact withtouch-sensitive surface 651, position 701 is offset from (x,y) position504 of stylus 203. The amount of the offset is optionally determinedbased on vertical distance 514 and optionally the positional state ofstylus 203.

FIGS. 7B-7C illustrate that, when stylus 203 moves laterally while beingheld above the touch-sensitive surface and within the threshold hoverdistance of the touch-sensitive surface (in other words, while stylus203 is within the hover range above the touch-sensitive surface),indicator 706 moves in accordance with the lateral movement of stylus203. In FIG. 7C, lateral movement of stylus 203 is stopped whenindicator 706 reaches user interface object 704. In response todetecting stylus 203 hovering above a location on the touch-sensitivesurface that corresponds to the location of user interface object 704,the device changes the appearance of user interface object 704 (e.g.,enlarges user interface object 704 slightly).

FIGS. 7D-7F illustrate that, when stylus 203 is moved vertically up anddown within the hover range, the device dynamically changes theappearance of user interface object 704 in accordance with the currenthover distance of stylus 203. In this example, the device enlarges thesize of user interface object 704 with decreasing hover distance (e.g.,represented by distance 514), and decreases the size of user interfaceobject 704 with increasing hover distance.

FIGS. 7G-7H illustrate that, while stylus 203 is within the thresholdhover distance of the touch-sensitive surface, lateral movement ofstylus 203 influences the shape of user interface object 704 whenindicator 706 is within a threshold distance (e.g., three quarters of adiameter of the user interface object) away from the original locationof user interface object 704 (e.g., the location of a centroid of theuser interface object). In other words, lateral movement of indicator706 away from the original location of user interface object 704stretches user interface object 704 in a movement direction of theindicator 706, until indicator 706 moves laterally beyond the thresholddistance away from the original location of user interface object 704.In some embodiments (not shown), the threshold distance is shorter whenstylus 203 is farther away from the touch-sensitive surface, and asmaller amount of stretch that can be applied to object 704 beforeobject 704 snaps back to its original shape.

FIG. 7I illustrates, that when indicator 706 moves beyond the thresholddistance away from the original location of user interface object 704,user interface object 704 snaps back into its original location andshape. In some embodiments, user interface object may be pull away fromits original location by a small distance with the movement of indicator706, but snaps back to its original location once indicator 706 movesbeyond the threshold distance away from the original location of object704.

FIG. 7J illustrates that stylus 203 makes an initial contact withtouch-sensitive surface 651. Upon initial contact of stylus 203 with thetouch-sensitive surface, the device changes the appearance of indicator706 to indicate that contact has been made and that user interfaceobject 704 is no longer in the hover state and interaction with the userinterface object will be carried out by a contact between stylus 203 andthe touch-sensitive surface. In addition, the device also changes theappearance of user interface object 704 (e.g., further enlarges userinterface object 704 as compared to the size before stylus 203 madecontact with the touch-sensitive surface, and highlighting userinterface object 704) to indicate that user interface object is nowbeing manipulated by a touch input, as opposed to a hover input. In someembodiments, the changes in the size of object 704 are continuous at thetransition between the object's states before and after stylus 203 madecontact with the touch-sensitive surface. In some embodiments, thedevice generates an audio output (e.g., audio signal 708) to indicatethat stylus 203 has made initial contact with the touch-sensitivesurface. The audio feedback (e.g., by audio signal 708) enhances thevisual feedback (e.g., enlarging and highlighting of user interfaceobject 704) to alert the user that object 704 has exited the hover stateand entered the contact state, and the user interface behavior will bedifferent in the contact state, as compared to the hover state. In someembodiments, if stylus 203 moves laterally while remaining in contactwith the touch-sensitive surface (not shown), indicator 706 moves inaccordance with the lateral movement of stylus 203, and drags object 704with it within user interface 702. In some embodiments, to distinguishfrom the dragging of the object by a hover input provided by stylus 203,object 704 moves at the same speed as indicator 706 and does not lagbehind indicator 706 in response to lateral movement of stylus 203 whilemaintaining contact with the touch-sensitive surface.

FIGS. 7K-7L illustrate that, when contact between stylus 203 and thetouch-sensitive surface is maintained for more than a threshold amountof time (e.g., T_(long) press) such that a long press input isregistered by the device (e.g., stylus 203 does not move for more than athreshold amount before the long press input is registered), userinterface object 704 is picked up by stylus 203. Upon detecting thatstylus 203 has maintained contact with the touch-sensitive surface formore than the long-press time threshold, the device changes theappearance of indicator 706 (e.g., from an open hand 706-b to a grabbinghand 706-c) to show that user interface object 704 is attached toindicator 706. The device provides a tactile output (e.g., discretetactile output 710) to indicate that user interface object 704 is pickedup and ready to be lifted up and moved with stylus 203. In someembodiments, the device shows that user interface object 704 appearingto jump up from its original z-location toward indicator 706. In someembodiments, generation of tactile output 710 is synchronized with theattachment of user interface object 704 to indicator 706.

FIGS. 7M-7R illustrate the process that user interface object 704 islifted up and moved with indicator 706 in response to movement of stylus203 while stylus 203 is hovering over the touch-sensitive surface. InFIGS. 7M-7O, after lift-off of stylus 203 from the touch-sensitivesurface, stylus 203 moves laterally while moving away from thetouch-sensitive surface. With increasing distance between stylus 203 andthe touch-sensitive surface (as indicated by increasing value ofdistance 514), the size of indicator 706 increases. In addition, withincreasing distance between stylus 203 and the touch-sensitive surface,the size of object 704 also increases accordingly. In FIGS. 7O-7P, it isshown that, with decreasing distance between stylus 203 and thetouch-sensitive surface, the size of indicator 706 decreases. Inaddition, with decreasing distance between stylus 203 and thetouch-sensitive surface, the size of object 704 also decreases.

In FIG. 7Q, the stylus is lifted above the touch-sensitive surface veryclose to the edge of the hover range (e.g., less than a thresholddistance (e.g., 10% of the threshold hover distance) from the edge ofthe hover range), the device generates visual feedback (e.g., flickeringedge 712 of indicator 702) indicating that stylus 203 is about to exitthe hover range and termination of the hover input is imminent if stylus203 is not brought closer to the touch-sensitive surface immediately(e.g., within a threshold amount of time (e.g., 300 ms)). In someembodiments, the device generates tactile output 714 (and/or an audioalert) in conjunction with displaying the visual feedback to indicatethat stylus 203 is about to exit the hover range. FIG. 7R shows thatstylus is brought closer to the touch-sensitive surface without exitingthe hover range, and the appearance of indicator 706 is restored (e.g.,flickering edge 712 ceases to be displayed). The size of object 704 isadjusted according to the current hover distance of stylus 203.

In FIGS. 7M-7R, it is illustrated that the size of object 704 isdynamically changed in accordance with the changes in the hover distanceof stylus 203, while object 704 is moved laterally in accordance withthe lateral movement of indicator 706 (and in accordance with thelateral movement of stylus 203 above the touch-sensitive surface). Inaddition, during the lateral movement of indicator 706, the movement ofobject 704 lags behind the movement of indicator 704 slightly, so whenindicator 706 changes its movement direction, or suddenly slows down orspeeds up, the relative positions of indicator 706 and object 704 changeslightly to reflect this lag.

FIG. 7S illustrates that, after stylus 203 picked up and moved userinterface object 704 (e.g., as shown in FIGS. 7M-7R), stylus 203 makescontact with the touch-sensitive surface again to drop off userinterface object 704. In some embodiments, upon detecting the secondcontact between stylus 203 and the touch-sensitive surface, the devicechanges the appearance of indicator 706 (e.g., from a grabbing hand706-c to an open hand 706-d) to indicate that object 704 is to bedropped off at the current location. In some embodiments, the deviceshows that object 704 detaches from indicator 706. The device optionallygenerates a tactile output (tactile output 716) in conjunction withobject 704 landing onto the surface of user interface 702.

FIG. 7T illustrates that, after dropping off object 704, stylus 203 islifted off the touch-sensitive surface and the appearance of indicator706 is changed to indicate that stylus 203 is in the hovering again. Ifat this time, stylus 203 moves laterally while hovering above thetouch-sensitive surface, object 706 will be stretched by the movingindicator 706 but will not move with indicator 706 (e.g., as illustratedearlier in FIGS. 7G-7H).

FIG. 7U illustrates that, after dropping off object 704 and being liftedoff of the touch-sensitive surface, stylus 203 is then lifted out of thehover range, such that stylus 203 is no longer in the hover state.Indicator 706 is no longer displayed, and object 704 is displayed at itsnew location and restored to its original appearance.

FIG. 7V-7AJ illustrates a process in which device 100 changes theappearance of object 704 in response to a continuous input that includesa first portion of the input in which stylus 203 is hovering above thetouch-sensitive surface, followed by a second portion of the input inwhich stylus 203 is in contact with the touch-sensitive surface,followed by a third portion of the input in which stylus is lifted offof the touch-sensitive surface and is in the hover state again. In thisexample, the device dynamically changes the appearance of object 704 inaccordance with the hover distance of stylus 203 in a first mannerbefore stylus 203 makes initial contact with the touch-sensitivesurface. The device dynamically changes the appearance of object 704 inaccordance with the contact intensity of stylus 203 in a second mannerafter stylus 203 makes the initial contact with the touch-sensitivesurface. In some embodiments, at least one change in appearance (e.g.,change in size of object 704) is continuous at the transition betweenthe hover state and the contact state. In some embodiments, at least onechange in appearance (e.g., change in color of object 704) is notcontinuous at the transition between the hover state and the contactstate. In addition, when stylus 203 breaks the initial contact with thetouch-sensitive surface, the device dynamically changes the appearanceof the object 704 in accordance with the hover distance of stylus 203.In some embodiments, at least one change in appearance (e.g., change insize of object 704) is continuous at the transition between the contactstate and the hover state. In some embodiments, at least one change inappearance (e.g., change in color of object 704) is not continuous atthe transition between the contact state and the hover state.

FIGS. 7U-7V illustrate that, when stylus 203 enters the hover range fromabove the touch-sensitive surface at a location that corresponds to thelocation of object 704 in user interface 702, the device displaysindicator 706 at the location of object 704 in user interface 702.

FIGS. 7V-7X illustrate that, when stylus 203 approaches thetouch-sensitive surface from above, device 100 increases the size ofobject 704 with decreasing hover distance (e.g., represented bydecreasing distance 514) of stylus 203 before stylus 203 makes initialcontact with the touch-sensitive surface. In some embodiments, devicealso increases the size of indicator 706 with the decreasing hoverdistance of stylus 203.

FIG. 7Y illustrates the initial contact of stylus 203 with thetouch-sensitive surface. In FIG. 7Y, it is shown that, as soon as stylus203 makes contact with the touch-sensitive surface and the contactintensity meets the detection threshold IT₀, the device changes theappearance of indicator 706 (e.g., from pointing hand 706-a to open hand706-b) to indicate that stylus 203 has exited the hover state and is nowin the contact state (and that the object under the influence ofindicator 706 or stylus 203 has exited the hover state and entered thecontact state). In addition, upon detecting the contact by stylus 203with the touch-sensitive surface (e.g., upon detecting that theintensity of the contact meets the detection threshold IT₀), device 100changes the appearance of object 704 (e.g., by highlighting object 704or changing the color of object 704) to indicate that object 704 willnow respond to change in contact intensity of the contact between stylus203 and the touch-sensitive surface. The transition from theun-highlighted state to the highlighted state is an abrupt change in theappearance of object 704 that occurs at the moment when stylus 203 makescontact with the touch-sensitive surface, or when contact intensityreaches to the contact detection intensity threshold IT₀. In someembodiments, in the intermediate stage before the stylus touches thetouch-sensitive surface and the contact intensity is below the detectionthreshold intensity IT₀, the device applies an animated transition tochange the size (e.g., to increase the size) of object 704 from thestate right before stylus 203 touches the touch-sensitive surface to thestate right after the intensity of contact between stylus 203 and thetouch-sensitive surface meets the detection intensity threshold IT₀. Inother words, the change in the size of object 704 (e.g., size increase)is a smooth transition when stylus 203 transitions from the hover stateto the contact state.

FIGS. 7Z-7AB illustrate that, while stylus 203 is in the contact withthe touch-sensitive surface, device 100 dynamically changes theappearance of object 704 in accordance with the characteristic intensityof the contact (e.g., shown as intensity of contact 655 in the intensitymeter) between stylus 203 and the touch-sensitive surface. For example,as shown in FIG. 7Z-7AB, the device increases the size of object 704with increasing intensity of the contact between stylus 203 and thetouch-sensitive surface. In some embodiments, when intensity of thecontact between stylus 203 and the touch-sensitive surface increases,the device optionally increases the size of indicator 706 as well.

It can be seen that, the size of object 704 continuously increases whenstylus 203 approaches touch-sensitive surface 651, makes contact withtouch-sensitive surface 651, and presses against touch-sensitive surface651 with increasing intensity. In other words, the increasing contactintensity in the contact state is treated as a continuation of thedecreasing hover distance in the hover state, when changing the size ofobject 704 first in accordance with the decreasing hover distance in thehover state and then in accordance with the increasing contact intensityin the contact state. In contrast, the color or highlighting of object704 goes through an abrupt transition when stylus 203 makes the initialcontact with the touch-sensitive surface. In other words, the deviceindicates the transition from the hover state to the contact state byapplying an abrupt change to the appearance of object 704.

FIG. 7AB also illustrates that, when intensity of the contact betweenstylus 203 and the touch-sensitive surface reaches a light pressintensity threshold IT_(L) (and the contact does not move for more thana threshold amount before the light press intensity threshold is met),device 100 performs an operation associated with object 704, such asdisplaying a menu 718 associated with object 704. In some embodiments,hint animations (e.g., visual changes to object 704 or user interface702 (e.g., blurring and darkening of user interface 702 except forobject 704)) are optionally displayed before intensity of the contactreaches the light press intensity threshold (e.g., after then intensityof the contact reaches a hint intensity threshold below the light pressintensity threshold).

FIGS. 7AB-7AD illustrate that, while stylus 203 remains in contact withthe touch-sensitive surface, stylus 203 gradually reduces the intensityof the contact with the touch-sensitive surface. While the intensity ofthe contact between stylus 203 and the touch-sensitive surface graduallydecreases, the device gradually reduces the size of object 704 inaccordance with the decreasing intensity of the contact between stylus203 and the touch-sensitive surface. In some embodiments, the devicealso gradually reduces the size of indicator 706 with the decreasingintensity of the contact between stylus 203 and the touch-sensitivesurface. In addition, in some embodiments, menu 718 remains to bedisplayed when intensity of the contact between stylus 203 and thetouch-sensitive surface gradually decreases.

FIG. 7AE illustrates that, when stylus 203 is about to lift-off from thetouch-sensitive surface, and the intensity of contact between stylus 203and the touch-sensitive surface has decreased to the contact detectionthreshold IT₀, the device determines that stylus 203 is about totransition from the contact state into the hover state again. Whenstylus 203 transitions from the contact state to the hover state, thesize of object 704 is the same as the size of object 704 when stylus 203transitioned from the hover state to the contact state right aftermaking the initial contact with the touch-sensitive surface.

FIGS. 7AE-7AH illustrate that, after stylus 203 makes the transitionfrom the contact state back to the hover state again, the deviceincreases the size of object 704 with increasing hover distance ofstylus 203. The size of indicator 706 increases with increasing hoverdistance of stylus 203. The changes in appearance of indicator afterlift-off of stylus 203 from the touch-sensitive surface is consistentwith the change in appearance of indicator 706 before stylus 203 madethe initial contact with the touch-sensitive surface. In other words,the size of indicator 706 increases with increasing hover distance ofstylus 203 regardless of whether it is before or after stylus 203 madethe initial contact with the touch-sensitive surface. In contrast to thebehavior of indicator 706, the changes in size of object 704 inaccordance with hover distance after the lift-off of stylus 203 from thetouch-sensitive surface is opposite to the changes in size of object 704in accordance with hover distance before stylus 203 made the initialcontact with the touch-sensitive surface. In other words, the size ofobject 704 increases with increasing hover distance of stylus 203 afterlift-off of stylus 203 from the touch-sensitive surface (e.g., as shownin FIGS. 7AF-7AH), while the size of object 704 increases withdecreasing hover distance of stylus 203 before stylus 203 made theinitial contact with the touch-sensitive surface (e.g., as shown inFIGS. 7V-7X).

FIG. 7AI illustrates that, when stylus 203 is within a thresholddistance (e.g., 10% of the threshold hover distance) away from reachingthe edge of the hover range, the device determines that stylus 203 isabout the exit the hover range if stylus 203 is not brought closer tothe touch-sensitive surface immediately (e.g., within 300 ms). Whendevice 100 detects that stylus 203 is about to exit the hover range,device 100 provides visual feedback (e.g., flickering edge 724 of object704) to indicate that stylus 203 is about to exit the hover range.

FIG. 7AJ illustrate that, when stylus 203 exits the hover range,indicator 706 is no longer displayed, and object 704 detaches fromindicator 706 and falls to the surface of user interface 702. The sizeof object 704 also snaps back to its original state. In someembodiments, device 100 generates a tactile output (e.g., tactile output726) in conjunction with object 704 snaps back into its original state.

FIG. 7AK-7AU illustrates a process in which an input object (e.g., afinger) moves and positions a cursor within selectable text (e.g.,editable or non-editable text) while the input object moves laterally inthe hover state, and in which the input object selects text (e.g.,expand text selection from the current cursor position) while the inputobject moves laterally in the contact state.

In FIG. 7AK, a user interface (e.g., user interface 730) is displayed ontouch-screen 112. User interface 730 includes selectable text 732. Whenthe input object, finger or hand 734, is above the threshold hoverdistance away from touch-screen 112 (e.g., distance 514 is greater thanthe threshold hover distance), no indicator corresponding to the inputobject is displayed in user interface 730.

FIG. 7AL illustrates that, when the input object (e.g., finger or hand734) is within the threshold hover distance from touch-screen 112, anindicator (e.g., cursor 738) is displayed within selectable text 732 atposition 701 on touch-screen 112 (e.g., at a location that correspondsto (x,y) position 504 on touch-screen 112). Position 701 is offset fromthe lateral position, (x,y) position 504, of finger 734, and the amountof offset is optionally determined based on the hover distance (e.g.,represented by distance 514) and/or a positional state (e.g., tilt) offinger 734. In some embodiments, in addition to cursor 738, device 100also displays a magnifying loupe (e.g., loupe 736) over selectable text732. Magnifying loupe 736 is displayed above cursor 734 in userinterface 730, and moves with cursor 732 in user interface 730. Withinmagnifying loupe 736, magnified version of a portion of selectable text732 is displayed, and a copy 742 of cursor 738 is also displayed at aposition within the magnified text according to the position of cursor738 within editable text 732.

FIG. 7AM illustrates that, as finger 734 moves laterally while remainingwithin the hover range, cursor 738 moves within selectable text 732 inaccordance with the lateral movement of finger 734. Magnifying loupe 736moves with cursor 738 and shows an updated portion of text 732 andupdated position of cursor 738. FIG. 7AM also illustrate that, the hoverdistance does not have to be maintained at a constant value during themovement of finger 734 in order to move cursor 738 within selectabletext 732.

FIG. 7AN illustrates that, as finger 734 moves laterally to anotherposition on touch-screen 112, cursor 738 is moved to a new positionwithin selectable text 732. Touch-down of finger 734 is detected ontouch-screen 112 (e.g., intensity of contact between finger 734 andtouch-screen 112 is above the contact detection threshold IT₀). Beforefinger 734 moves laterally while in contact with touch-screen 112,cursor 732 is displayed at its current location within selectable text732. Magnifying loupe 742 is displayed above cursor 732. Magnifiedversion of the text surrounding cursor 732 is displayed withinmagnifying loupe 736, and position of cursor 732 within the selectabletext is represented by copy 742 of cursor 736 within the magnifyingloupe.

FIG. 7AO illustrates that, after finger 734 makes contact withtouch-screen, finger 734 moves laterally while remaining in contact withtouch-screen 112. The movement of the contact causes cursor 738 to movewithin selectable text 732, and movement of cursor 738 from its previouslocation (e.g., the cursor location at the time of the touch-down offinger 734 on touch-screen 112) to its current location causes a portionof text between the cursor's previous location and current location tobe selected (e.g., as indicated by selection 740). As movement of cursor738 continues with the movement of contact between finger 734 andtouch-screen 112, selection 740 is expanded or contracted in accordancewith the movement of cursor 738. As shown in FIG. 7AO, selection 740 isalso represented (e.g., as selection 744) within magnifying loupe 736.

FIG. 7AP illustrates that, after moving the contact between finger 734and touch-screen 112 and adjusting the ending boundary of selection 740by the moving cursor 738, lift-off of finger 734 is detected. Afterlift-off from touch-screen 112, finger 734 is hovering abovetouch-screen 112 again. While finger 734 hovers above touch-screen 112,cursor 738 detaches from selection 740, and moves within selectable text732 with the lateral movement of finger 734 while finger 734 remainswithin the hover range above touch-screen 112. As shown in FIG. 7AP, insome embodiments, selection 740 is maintained in text 732 after lift-offof contact between finger 734 and touch-screen 112 is detected.Magnifying loupe continues to move with cursor 732, and displays amagnified version of the text surrounding cursor 738.

FIG. 7AQ illustrates that, cursor 738 has moved to a new location withintext 732 in accordance with lateral movement of finger 734 while finger734 is within the hover range above touch-screen 112. Magnifying loupe736 is also moved with the moving cursor 736 and displays a magnifiedversion of the text surrounding cursor 738. Selection 740 is stillmaintained at its original location.

FIGS. 7AR-7AS illustrate that, when touch-down of finger 734 is detectedagain at a new location, selection 740 is canceled (selection 740 is nolonger shown in FIG. 7AR). Cursor 738 is displayed at the new location(e.g., position 701) that corresponds to the touch-down location (e.g.,(x,y) position 504) of finger 734 on touch-screen 112, as shown in FIG.7AR. In FIG. 7AS, lateral movement of finger 734 across touch-screen 112is detected, and movement of cursor 738 from its previous location(e.g., location of cursor 738 at the time of the second touch-down offinger 734 in FIG. 7AR) to its current location causes a portion of textbetween the previous location and the current location of cursor 738 tobe selected (e.g., as shown by selection 746). Magnifying loupe 736moves with cursor 738 and shows the current selection of text (e.g.,represented by magnified copy 748 of selection 746).

FIG. 7AT shows that, lift-off of finger 734 is detected, and cursor 738is detached from selection 746 in response to the lift-off of finger 734from touch-screen 112. Selection 746 is maintained while cursor 738moves away from selection 746 in accordance with movement of finger 734.

FIG. 7AU illustrates that, when finger 734 is lifted out of the hoverrange (e.g., beyond the threshold hover distance above touch-screen112), magnifying loupe 736 is replaced with menu 750 (e.g., a“cut/copy/lookup” menu) and selection 746 changes appearance (e.g.,replaced with selection object 752 with adjustable boundaries). Theselection object 752 is optionally moved by a contact (e.g., anothercontact by finger 734) as a whole to another location, or resized by acontact (e.g., another contact by finger 734) the drags the adjustableboundaries of selection object 752. In some embodiments, when selectionobject 752 is displayed, device 100 optionally does not display cursor738 when finger 734 re-enters the hover range. In some embodiments, atap input by a contact (e.g., another contact by finger 734) dismissesmenu 750 and cancels selection represented by selection object 752, anda subsequent hover input, when detected, causes display and placement ofcursor 738 again in the manner illustrated in FIGS. 7AK-7AT.

FIGS. 8A-8V illustrate user interface interactions for moving an object(e.g., application launch icon 806, or a moveable boundary or selectionhandle 838 of a content selection object) in a user interface (e.g.,home screen user interface 802, or content-display user interface 830)in accordance with some embodiments. In particular, FIGS. 8A-8Villustrate that, when the object is moved across the user interface inaccordance with a lateral movement of an input object while the inputobject hovers above the touch-sensitive surface, the move of the objectis canceled when the input object is lifted out of the hover proximityrange without first making contact with the touch-sensitive surface, andthe move of the object is confirmed when the input object makes contactwith the touch-sensitive surface after the lateral movement.

FIG. 8A shows a user interface (e.g., home screen user interface 802)that includes a number of user interface objects that correspond todifferent applications installed on the electronic device 100 (e.g.,application launch icon 806 that corresponds to a “Calculator”application, and folder icon 808 that corresponds to a folder thatincludes one or more application launch icons, application launch icon810 that corresponds to a telephony application, application launch icon812 that corresponds to a mail application, application launch icon 814that corresponds to an Internet browser application, etc.). The userinterface objects are arranged in the user interface in accordance witha predetermined layout (e.g., according to a four column grid). Some ofthe objects (e.g., applications launch icons 810, 812, and 814) areincluded in a container object (e.g., dock 804).

In FIG. 8B, a home screen reconfiguration mode has been triggered andapplication launch icon 806 is currently selected, e.g., in response toa long press input by contact 814 with the touch-sensitive surface. Inthe home screen reconfiguration mode, the icons in the home screen userinterface can be rearranged by moving one or more of the icons.

FIGS. 8C-8F illustrate that the selected icon 806 is dragged across theuser interface in accordance with lateral movement of the input object(e.g., hand or finger 734) while the input object hovers over thetouch-sensitive surface 112. In some embodiments, a visual indication ofthe hovering input object (e.g., indication 816) is displayed on thetouch screen. In some embodiments, indication 816 is not visible on thetouch screen. In FIG. 8C, when icon 806 is moved out of its originallocation in the home screen user interface 802, other icons (e.g., icon808) are rearranged in the home screen user interface 802 in accordancewith predefined user interface layout rules. In FIG. 8D, when icon 806is dragged near the dock 804, other icons (e.g., icons 810, 812 and 814)within the dock 804 are rearranged to make room for icon 806.

FIGS. 8C-8F also illustrate that, during the lateral movement of finger734 while finger 734 hovers above touch-screen 112, the appearance ofthe 806 is dynamically changed in accordance with hover distance 514 offinger 734. For example, when finger 734 hovers higher abovetouch-screen 112 (e.g., as in FIGS. 8C-8D), icon 806 appears moreenlarged than when finger 734 hovers lower above the touch-screen (e.g.,as in FIGS. 8E-8F).

FIGS. 8G-8H illustrate that, after the icon 806 is moved across thetouch-screen in accordance with the lateral movement of the hoveringfinger 734, finger 734 makes contact with the touch-screen at a locationthat corresponds to an acceptable drop-off location for icon 806 on thetouch-sensitive surface (as shown in FIG. 8G). As a result, the icon 806is dropped off at the acceptable drop-off location that corresponds tothe location of contact 818 on touch-screen 112 and remains at the newlocation after lift-off of the contact 818 (e.g., as shown in FIG. 8H).The move of icon 806 and rearrangement of home screen user interface 802is confirmed and completed, and the locations of the icons on the homescreen user interface remains in the new configuration after the finger734 is lifted out of the hover proximity range.

In contrast to the scenario illustrated in FIGS. 8G-8H, FIGS. 8I-8Jillustrate that, after icon 806 is moved across the touch screen inaccordance with the lateral movement of the hovering finger 734, finger734 is lifted out of the hover-proximity range before finger 734 hasmade any contact with the touch-screen (as shown in FIG. 8I, ascontinuation of any of FIGS. 8C-8F). As a result, icon 806 flies back toits original location in home screen user interface 806, as do othericons (e.g., icons 808, 810, 812, and 814) that have been moved inresponse movement of icon 806; and the movement of icon 806 and therearrangement of the home screen user interface is canceled (e.g., asshown in FIGS. 8I-8J). In other words, after a preview of therearrangement of the home screen user interface has been presented tothe user, the rearrangement of the home screen user interface isreverted when the hover input ended without finger 734 making contactwith touch-screen 112 first.

FIGS. 8K-8M illustrate that, icon 806 is dragged by a continuouslymaintained contact 820 from its original location (in FIG. 8K) to thesame drop-off location as before (e.g., same drop-off location in FIGS.8F and 8M). When icon 806 is dragged, other icons in the home screenuser interface 112 are also rearranged in response to the movement oficon 806 (e.g., as shown in FIGS. 8L and 8M).

Following FIGS. 8K-8M, in FIGS. 8N-8O, finger 734 is lifted offtouch-screen 112 and lifted out of the hover proximity range above thetouch-screen, and icon 806 remains in its new position in the dock 804,and the home screen user interface remains in the new configuration.

FIG. 8P shows a content-display user interface 830 (e.g., a userinterface of a text editor application or a web-browser application).Content-display user interface 830 displays selectable text. Withincontent-display user interface 830, a portion of text is currentlyselected, as indicated by text selection box 843 that includes theportion of the selected text. Text selection box 843 includes abeginning edge (e.g., selection handle 836) and an ending edge (e.g.,selection handle 838).

FIG. 8Q shows that one of the two selection handles (e.g., selectionhandle 838) is selected (e.g., by contact 842 made by finger 734 withthe touch-screen) for subsequent movement. In some embodiments, theselection handle 838 is selected by another required input, such as apredefined hover gesture (e.g., an in-air finger wiggle gesture) whilefinger 734 hovers above selection handle 838 (e.g., when (x,y) position504 of finger 734 corresponds to the location of selection handle 838).The selection of selection handle 838 is visually indicated byenlargement of the end portion of selection handle 838 relative to acorresponding end portion of selection handle 836. In addition, amagnifying object (e.g., magnifying loupe 840) is displayed near theselected selection handle 838 to show a portion of the text near theselected selection handle 838. In some embodiments, cursor 844 isdisplayed within the text shown in magnifying loupe 840 to indicate theboundary of the text selection box.

FIG. 8R shows that, in accordance with lateral movement of finger 734while finger 734 hovers above touch-screen 112 (e.g., an indication 846of the hovering finger 734 is shown to indicate the relative position ofthe hovering finger 734 and the selected selection handle 38), theselected selection handle 838 is moved across the touch-screen relativeto the unselected selection handle 836, changing the size of textselection 834 (e.g., expanding text selection 834).

FIGS. 8S-8T illustrate that, after the selected selection handle 838 ismoved with hovering finger 734 (as shown in FIGS. 8Q-8R), finger 734makes contact with touch-screen 112 and as a result, the relocation ofselection handle 838 and the resizing of text selection object 834 areconfirmed and remain in effect after finger 734 is lifted out of thehover proximity range above touch-screen 112 (e.g., as shown in FIG.8T).

FIGS. 8U-8V illustrate that, in contrast to the scenario shown in FIGS.8S-8T, after the selected selection handle 838 is moved with thehovering finger 734 (as shown in FIGS. 8Q-8R), finger 734 is lifted outof the hover proximity range without first making contact withtouch-screen 112, and as a result, the relocation of selection handle838 and the resizing of text selection object 834 are canceled whenfinger 734 is lifted out of the hover proximity range above touch-screen112.

FIGS. 9A-9O illustrate user interactions by an input object to displaytransient visual effect (e.g., a precursor image 906 or visual hint ofquick action menu 914, mini application object 912) and maintainingdisplay of the transient visual effect (e.g., the transient userinterface object(s)) by maintaining the input object within the hoverproximity range above touch-screen 112. In addition, the transientvisual effect that is displayed when the input object is hovering intoward the touch-screen (e.g., when the input object is entering thehover proximity range from outside of the hover-proximity range, andmoving within the hover proximity range before making contact with thetouch-screen) is different from the transient visual effect that isdisplayed when the input object is hovering out away from thetouch-screen (e.g., when the input object is on its way to exit thehover proximity range after making contact with the touch-screen). Insome embodiments, by making contact with the touch-sensitive surface andlifting off, an operation is activated (e.g., launching an application,or activating a menu option) by the input object. In some embodiments,with a quick lift-off of the contact by the input object, the operationis performed without displaying the transient visual effect during thebrief time that the input object is moving through the hover proximityrange.

FIG. 9A shows a user interface (e.g., home screen user interface 902)that includes a number of objects (e.g., application launch icons,including application launch icon 904 for an instant messagingapplication).

FIG. 9B illustrates that, when an input object (e.g., finger 734) hoversabove application icon 904, a precursor image (e.g., preview platter906) of a quick action menu 914 and a mini application object 912 isdisplayed. Relative positions of indication 908 of the input object andicon 904 on the touch-screen are shown in FIG. 9B. In some embodiments,the size and appearance of the precursor image changes dynamically withhover distance 514 of the hovering finger 734. FIG. 9B also shows thatportions of home screen user interface 902 outside of icon 904 aredarkened and blurred when finger 734 is detected hovering abovetouch-screen 112, as a hint to indicate that icon 904 is anintensity-reactive icon which will provide an object-specific response(e.g., show a quick action menu and a mini application object thatcorrespond to the instant messaging application) in response to a lightpress input (e.g., as opposed to a tap input). In some embodiments, theamount of darkening and blurring applied to home screen user interface902 changes dynamically with hover distance 514 of the hovering finger734. Although not shown, the display of the precursor image and the hintvisual effect (e.g., the blurring and darkening of home screen userinterface 902) are transient, and cease to be displayed when finger 734is lifted out of the hover proximity range above the touch-screen beforefinger 734 has made any contact with the touch-sensitive surface.

FIGS. 9C-9D illustrate that, when finger 734 makes contact (e.g.,contact 910) with touch-screen 112 and increase the intensity of thecontact (e.g., contact 910), the precursor image and the hint visualeffect are further enhanced (e.g., preview platter 906 is enlarged andshifted off-center, and the blurring and darkening of home screen userinterface 902 are increased). In some embodiments, the visual effectsthat are shown is continuous and non-discrete when finger 734 movestoward the touch-screen, makes contact with the touch-screen, andpresses against the touch-screen. Although not shown here, when finger734 is lifted off the touch-screen before the intensity of contact 910exceeds the light press intensity threshold IT_(L), the device treatsthe received input by finger 734 as a tap input, and launches theapplication in response to detecting lift-off of contact 910.

FIG. 9E illustrates that when a characteristic intensity of the contact(e.g., contact 910) by finger 734 exceeds the light press intensitythreshold IT_(L) (as indicated by intensity meter 901), the precursorimage (e.g., preview platter 906) is transformed into mini applicationobject 912 and quick action menu 914 (e.g., a list of selectableoptions) that correspond to the instant messaging application. Theblurring and darkening of the home screen user interface behind miniapplication object 912 and quick action menu 914 are at their maximumextent when mini application object 912 and quick action menu 914 arefirst displayed.

FIG. 9F shows that when finger 734 is lifted off touch-screen 112 butstill remains within the hover proximity range above the touch-screen,mini application object 912 and quick action menu 914 remain displayedover the blurred and darkened home screen user interface 902. Theappearances of mini application object 912 and quick action menu 914 arechanged with the changing hover distance of finger 734 to indicate thatthe display of mini application object 912 and quick action menu 914 istransient and will cease once finger 734 is lifted out of the hoverproximity range above touch-screen 112. For example, mini applicationobject 912 and quick action menu 914 become increasingly translucent asfinger 734 moves away from the touch-screen. In some embodiments, miniapplication object 912 and quick action menu 914 are lifted off thez-layer of the home screen user interface with the hovering finger 734and optionally quiver with the lateral movement of finger 734 while thefinger hovers above touch-screen 112.

FIGS. 9G-9H illustrate that, before finger 734 is lifted out of thehover proximity range and while mini application object 912 and quickaction menu 914 are still visible over home screen user interface 902,finger 734 moves downward and makes contact (e.g., as indicated bycontact 918 on application launch icon 904) with touch-screen 112 (asshown in FIG. 9G); and in response to detecting finger 734 makingcontact with touch-screen 112 and upon lift-off of finger 734 fromtouch-screen 112 (e.g., in some embodiments, a quick lift-off withminimal hovering is required), the device launches the instant messagingapplication (as shown in FIG. 9H). In some embodiments, the instantmessaging application is launched to display a user interface thatcorresponds to the item at the location of the contact (e.g., contact918). For example, contact 918 is on the application launch icon 904,and the application is launched to display conversation listinginterface 920 of the instant messaging application upon lift-off of thecontact (or upon detecting that finger 734 has exited the hoverproximity range within a threshold amount of time after lift-off ofcontact 918). If the contact is on one of the avatars in miniapplication object 912, the device optionally launches the instantmessaging application to display a conversation interface thatcorresponds to the avatar. If the contact is on one of the selectableoptions in quick action menu 914, the device launches a user interfacethat corresponds to the selectable option. FIG. 9G shows that, miniapplication object 912 and quick action menu 914 are restored to theiroriginal appearances upon contact of finger 734 with the touch-screen.In some embodiments (not shown), the user can move the contact (e.g.,contact 918) to a desired location on the touch-screen (e.g., over oneof the selectable options in the quick action menu or one of the avatarsin the mini application object), and then lift off from that location tocause the application to be launched to display a corresponding userinterface. In some embodiments, the device requires finger 734 to exitthe hover proximity range within a threshold amount of time afterlift-off of the contact in order to launch the application; otherwise,the transient user interface objects (e.g., the quick action menu andthe mini application object) will be displayed while the finger reentersthe hover proximity range and remains within the hover proximity rangeabove the touch-screen.

FIG. 9I illustrates that, instead of moving closer to the touch-screenand making contact with the touch-screen, if finger 734 moves furtheraway from the touch-screen but remains within the hover proximity rangeabove the touch-screen, mini application object 912 and quick actionmenu 914 become increasingly translucent (e.g., more so than that shownin FIG. 9F) as finger 734 moves away from the touch-screen. In addition,mini application object 912 and quick action menu 914 are lifted off thehome screen user interface with the hovering finger 734 leaving a longershallow on the home screen user interface. FIG. 9I also shows that, whenmini-application object 912 and become more translucent, the amount ofblurring and darkening applied to home screen user interface 902 arealso reduced, indicating to the user that home screen user interface 902will be fully restored if finger 734 continues to move away from thetouch-screen and exits the hover proximity range above the touch-screen.

FIG. 9J illustrate that the transient user interface objects that aredisplayed during the hovering in process (e.g., when the input object ismoving toward the touch-screen and moving into the hover proximityrange) and during the hovering out process (e.g., when the input objectis moving away from the touch-screen and moving out of the hoverproximity range) are different, and that the appearances of thetransient user interface objects may change in different ways inresponse to the changing hover proximity parameter of the input object.In the top row of FIG. 9J, when finger 734 has just entered the hoverproximity range above the touch-screen and has not make any contact withthe touch-screen, a preview platter is displayed behind the applicationlaunch icon (e.g., as shown in (A)); the preview platter grows largerwhen the finger moves closer to the touch-screen (e.g., as shown in(B)); and when the finger presses against the touch-screen, the previewplatter expands and shifts, and eventually transforms into the miniapplication object and the quick action when the intensity of thecontact exceeds the light press threshold (as shown in (C)). In thebottom row of FIG. 9J, after the finger has made contact with thetouch-screen and after the mini application object and the quick actionmenu have been displayed, moving the finger away from the touch-screenmakes the mini application object and the quick action menu increasinglytranslucent indicating that they would cease to be displayed once thefinger is lifted out of the hover proximity range above the touch-screen(e.g., as shown in (D) and (E); and moving the finger toward thetouch-screen makes the mini-application object and the quick action menuincreasingly opaque indicating that they will be restored completely totheir initial appearances when the finger makes contact with thetouch-screen again (as shown in (F)).

FIG. 9K continues from FIG. 9E, where after mini application object 912and quick action menu 914 have been displayed in response to detectingthe intensity of contact 910 exceeding the light-press intensitythreshold (as indicated by intensity meter 901), intensity of thecontact is decreased and mini application object 912 and quick actionmenu 914 maintain their original appearance as long as the contact ismaintained.

FIGS. 9L and 9M illustrate that a quick lift-off (e.g., the speed offinger 734 exceeding a first threshold speed and/or finger 734 exitingthe hover proximity range within a threshold amount of time), thetransient user interface objects (e.g., mini application object 912 andquick action menu 914) cease to be displayed even while finger 734 isstill moving through the hover proximity range above touch-screen 112(as shown in FIG. 9L).

FIGS. 9N-9O continue from FIG. 9E or 9I, where finger 934 has not madecontact with touch-screen 112 again after the display of miniapplication object 912 and quick action menu 914. FIGS. 9N-9O illustratethat, when finger 934 is lifted out of the hover proximity range slowly(e.g., the speed of finger 734 is below a second threshold speed and/orfinger 734 lingers within the hover proximity range for more than athreshold amount of time), the transient user interface objects (e.g.,mini application object 912 and quick action menu 914) remain displayedfor a brief moment even after finger 734 has exited the hover proximityrange above touch-screen 112 (as shown in FIG. 9N). FIG. 9O shows that,the transient user interface objects only linger for a brief moment(e.g., 200 ms) and cease to be displayed after that brief moment haspassed. In some embodiments (not shown), if finger 734 reenters thehover proximity range, the device maintains display of the transientuser interface object and interprets the exit of finger 734 asaccidental and ignores it.

In some embodiments, FIG. 9K continues from FIG. 9G, where finger 934has made contact with touch-screen 112 again after the display of miniapplication object 912 and quick action menu 914, when finger 934 islifted out of the hover proximity range sufficiently slowly (e.g., thespeed of finger 734 is below a second threshold speed and/or finger 734lingers within the hover proximity range for more than a thresholdamount of time). In such cases, no application launching operation isactivated upon lift-off of the contact, and the transient user interfaceobjects (e.g., mini application object 912 and quick action menu 914)remain displayed after finger 734 is lifted off touch-screen 112.

FIGS. 10A-10Y illustrate different device responses to input objectentering and/or exiting different levels of hover proximity ranges inaccordance with some embodiments.

10A-10E illustrate displaying a tool bar when finger 734 enters a firsthover-proximity range from outside of the first hover proximity range,and activating or highlighting a control in the tool bar when finger 734enters a second hover proximity range from outside of the second hoverproximity range, where the first hover proximity range is a bigger rangethat includes the second hover proximity range. For example, the firsthover proximity range corresponds to a larger threshold hover distance(e.g., threshold hover distance 1) above the touch-screen, and thesecond hover proximity range corresponds to a smaller threshold hoverdistance (e.g., threshold hover distance 2) above the touch-screen.

FIG. 10A shows a user interface (e.g., browser user interface 1002).Browser user interface 1002 displays content of a web page. Browser userinterface 1002 is displayed in a full-screen mode without showing anymenu bars or tool bars of the browser application.

FIG. 10B shows that when finger 734 enters the first level hoverproximity range from outside of the first level hover proximity range,while the (x,y) position 504 of finger 734 is within a predefined loweredge portion of touch-screen 112 (e.g., as indicated by indication 1004of finger 734 relative to touch-screen 112), the displayed content inbrowser user interface 1002 is shifted as a whole upward away from thelower edge of the touch-screen and a tool bar (e.g., tool bar 1006) isdisplayed in the space vacated by the shifted content. In someembodiments (not shown), when finger 734 then moves out of the firstlevel hover proximity range without first entering the second levelhover proximity range, the displayed content shifts back down toward thelower edge of the touch-screen and the tool bar ceases to be displayed.It is noted that indication of finger 734 is not visible on thetouch-screen in some embodiments.

FIG. 10C illustrates that, when finger 734 continues to move toward thetouch-screen while remaining near the bottom edge of the touch-screen(as indicated by indication 1004 of finger 734 relative to touch-screen112) and upon finger 734 entering the second level hover proximity rangefrom outside of the second level hover proximity range, a controlaffordance (e.g., affordance 1008 for sharing the displayed content) intool bar 1006 that is nearest finger 734 is highlighted and enlarged. Insome embodiments, if finger 734 does not continue to move toward thetouch-screen, but exits the second level hover proximity range by movingaway from the touch-screen, the highlighting on control affordance 1008is removed and control affordance 1008 is restored to its originalappearance. While finger 734 still remains within the first level hoverproximity range, tool bar 1006 remains displayed with all itsaffordances in their original appearances. In some embodiments (notshown), if finger 734 moves laterally to a hover location over anothercontrol affordance in tool bar 1006 while finger 734 remains within thesecond level hover proximity range, the control affordance that isnearest finger 734 is highlighted and enlarged instead of affordance1008.

FIGS. 10D-10E illustrate that, when finger 734 makes contact with thetouch-screen at a touch location that corresponds to a controlaffordance in tool bar 1006 (e.g., indicated by contact 1010 on thehighlighted control affordance 1008), an operation corresponding to theselected control affordance 1008 is performed (e.g., a sharing card 1012showing various sharing options is displayed). In some embodiments (notshown), after tool bar 1006 is displayed, moving finger 734 toward thetouch-screen does not highlight any control affordance, and a controlaffordance is activated only when finger 734 makes contact with thetouch-screen at a touch location that corresponds to the controlaffordance.

FIGS. 10F-10M illustrate displaying a control panel that includes one ormore control affordances when finger 734 enters a first hover-proximityrange from outside of the first hover proximity range, and highlightinga control in the tool bar when finger 734 enters a second hoverproximity range from outside of the second hover proximity range, inaccordance with some embodiments.

FIG. 10F shows a media player application operating in a full-screenplayback mode. User interface 1020 of the media player applicationdisplays a video in playback mode.

FIG. 10G illustrates that, when finger 734 moves toward the touch-screenand enters the first level hover proximity range, a control panel (e.g.,control panel 1023) with three playback control affordances (e.g.,rewind affordance 1024, pause affordance 1026, and fast forwardaffordance 1028) is displayed on media player user interface 1020, whilethe video continues to be played. The location of control panel 1023 isselected based on (x,y) position 504 of finger 734. For example, thecenter of control panel 1023 is placed slightly above the (x,y) position504 of finger 734 (e.g., the (x,y) position of finger 734 is indicatedby indication 1030 relative to touch-screen 112). It is noted thatindication of finger 734 is not visible on the touch-screen in someembodiments. FIG. 10G further shows that, scrubber 1022 is displayed atthe top of user interface 1020 to indicate current progress of the videoplayback. The location of scrubber 1022 is predefined and does notdepend on the (x,y) position 504 of finger 734.

FIG. 10H illustrates that, when finger 734 moves laterally whilehovering within the first level hover proximity range (without enteringthe second level hover proximity range), control panel 1023 isrepositioned on the touch-screen in accordance with the (x,y) position504 of finger 734.

FIG. 10I illustrates that, when finger 734 moves closer to thetouch-screen and enters the second level hover proximity range, acontrol affordance (e.g., rewind affordance 1024) nearest finger 734 ishighlighted relative to other control affordances in control panel 1023.

In FIG. 10J, when finger 734 moves laterally while remaining within thesecond level hover proximity range, control panel 1023 remainsstationary, and a different control affordance (e.g., pause affordance1026) that is closest to finger 734 becomes highlighted instead.

FIG. 10K illustrates that, when finger 734 makes contact (e.g.,indicated by contact 1032) with a control affordance (e.g., pauseaffordance 1026) in control panel 1023, the control affordance isactivated (e.g., pause affordance 1026 is toggled into play affordance1026′). In some embodiments, the control affordance is activated uponcontact. In some embodiments, the control affordance is activated uponlift-off of the contact.

FIG. 10L illustrates that, when finger 734 is lifted off thetouch-screen after making contact with pause control 1026, and returnedto the first hover proximity range after exiting the second hoverproximity range, the highlighting of control affordance ceases to bedisplayed, and control panel 1023 remains displayed at a location thatcorresponds to (x,y) position 504 of finger 734 (e.g., as indicated byrelative position of control panel 1023 and indication 1034 of finger734).

In FIG. 10M, after finger 734 has exited the first level hover proximityrange, control panel 1023 and scrubber 1022 cease to be displayed, andvideo playback in user interface 1020 remains in the paused state.

FIGS. 10N-10R illustrate displaying information (e.g., missednotifications) for an application or applications in a folder whenfinger 734 hovers over an application icon or folder icon within a firstlevel hover proximity range, and displaying more details of theinformation (e.g., details of the missed notifications) when finger 734enters the second hover proximity range from outside of the second hoverproximity range, in accordance with some embodiments.

FIG. 10N shows home screen user interface 1042 that includes applicationlaunch icons and a folder icon 1044. A badge (e.g., the indicator “4”)on folder icon 1044 indicates there are a number of unread notifications(e.g., four unread notifications) for the applications within the folderrepresented by folder icon 1044.

FIG. 10O shows that, when finger 734 moves toward the touch-screen andenters the first level hover proximity range near the location of foldericon 1044 (e.g., as indicated by the relative positions of folder icon1044 and indication 1046 for the (x,y) position 504 of finger 734),notification list 1048 is displayed near folder icon 1044. Notificationlist 1048 includes a count of unread notifications for each applicationwithin the folder that have unread notifications. Optionally, portionsof home screen user interface 1042 outside of folder icon 1044 aredarkened and blurred underneath notification list 1048. In this example,three of the five applications in the folder have unread notifications,e.g., the App Store application has one unread notification, theMessages application has two unread notifications, and the Mailapplication has one unread notification. In some embodiments (notshown), if finger 734 exits the first level hover proximity range bymoving away from the touch-screen now, notification list 1048 will ceaseto be displayed, and the notifications remain as unread.

FIG. 10P shows that, when finger 734 moves closer toward thetouch-screen and enters the second level hover proximity range near thelocation of folder icon 1044 (or near any portion of notification list1048), more details of the unread notifications are displayed. Forexample, content for each unread notification is displayed in expandednotification list 1050. In some embodiments, if finger 734 is liftedaway from the touch-screen and exits the second level hover proximityrange, expanded notification list 150 remains displayed as long asfinger 734 still remains within the first level hover proximity range.In some embodiments, if finger 734 is lifted away from the touch-screenand exits the second level hover proximity range, expanded notificationlist 1050 ceases to be displayed and notification 1048 is redisplayed aslong as finger 734 still remains within the first level hover proximityrange. In some embodiments, once finger 734 is lifted out of the firstlevel hover proximity range, no notification list is displayed, and thestatus of the previously unread notifications is changed to “read” bythe device.

FIG. 10Q illustrates that, if finger 734 does not exit the first levelhover proximity range, but instead makes contact with the touch-screen(e.g., contact 1052 is detected on folder icon 1044), expandednotification list 1050 remains displayed while contact 1052 ismaintained on the touch-screen. In some embodiments, if lift-off ofcontact 1052 is detected while contact 1052 is on folder icon 1044,display of home screen user interface 1042 and expanded notificationlist 1052 is replaced with or partially replaced with content of thefolder represented by folder icon 1044. In some embodiments, if, insteadof a folder icon, the finger hovered over an application launch iconthat corresponds to an application that has unread notifications,lift-off of finger 734 after the finger makes contact with theapplication launch icon causes the application to be launched, andcauses display of the user interface of the application to replace thedisplay of the home screen user interface.

FIGS. 10R-10S illustrate that, while finger 734 maintains contact (e.g.,contact 1052) with the touch-screen, finger 734 moves across thetouch-screen to a new location over an unread notification for theMessages application; and in response to detecting lift-off of contact1052 over the unread notification for the Messages application, thedevice replaces the display of home screen user interface 1042 andexpanded notification list 1050 with user interface 1062 of the messagesapplication that corresponds to a conversation associated with themissed notification. Although not shown, in some embodiments, theread/unread statuses of all of the previously unread notifications shownin notification list 1050 are changed to “read” by the device. In someembodiments, the statuses of the unread notifications for otherapplications (e.g., App Store and Mail) within the folder remain asunread.

FIGS. 10T-10Y illustrate activating a cursor placement mode when finger734 hovers over selectable content within a first level hover proximityrange, and activating a selection resize mode when finger 734 enters asecond hover proximity range from outside of the second hover proximityrange, in accordance with some embodiments.

In FIG. 10T, user interface 1072 displays content (e.g., selectabletext).

FIG. 10U, when finger 734 moves toward the touch-screen and enters thefirst level hover proximity range, cursor 1074 is displayed within thedisplayed text at a location that corresponds to (x,y) position 504 offinger 734 (e.g., as indicated by indication 1076 (not visible))relative to touch-screen 112. In addition, a magnifying loupe (e.g.,magnifying loupe 1078) is displayed. A magnified version of a portion ofthe text near cursor 1074 is shown in magnifying loupe 1078. A magnifiedversion 1080 of cursor 1074 is also shown in magnifying loupe 1078.

FIG. 10V shows that, when finger 734 moves laterally within the firstlevel hover proximity range, cursor 1076 and magnifying loupe 1078 moveacross the touch-screen in accordance with (x,y) position 504 of finger734. In some embodiments (not shown), if finger 734 is lifted out of thefirst level hover proximity range, cursor 1076 and magnifying loupe 1078cease to be displayed. In some embodiments, the cursor placement modecan be activated when a selection already exist within the content. Insome embodiments, cursor 1074 remains displayed (e.g., at least for athreshold amount of time) and the magnifying loupe ceases to bedisplayed when finger 734 is lifted out of the first level hoverproximity range without first entering the second level hover proximityrange. For example, the user can start typing or pasting additionalcontent at the position of the cursor afterwards. Cursor 1074 may ceaseto be displayed if no user input is detected within the threshold amountof time.

FIG. 10W shows that, when finger 734 continues to move toward thetouch-screen and enters the second level hover proximity range, theappearance of cursor 1074 changes to indicate that selection resize modeis activated. For example, cursor 1074 transforms into two overlappingselection handles 1084 and 1086. The appearance of magnifying loupe 1978is changed (e.g., changed to magnifying loupe 1088) to indicate that theselection resize mode is activated.

FIGS. 10X-10Y show that, once the selection resize mode has beenactivated, subsequent lateral movement of finger 723 within the secondlevel hover proximity range causes text to be selected (e.g., inselection object 1082) with one selection handle (e.g., selection handle1086) remaining at its initial location, and the other selection handle(e.g., selection handle 1084) moving in accordance with the lateralmovement of finger 723. Magnifying loupe 1088 moves with the selectionhandle (e.g., selection handle 1084) that is repositioned by finger 734.In some embodiments (not shown), after the text selection has beenexpanded, if finger 743 is lifted out of the second hover proximityrange and then out of the first hover proximity range without firstmaking contact with the touch-screen, the selection is canceled; and iffinger 734 first makes contact with the touch-screen, the selection ismaintained after finger 734 is lifted out of the second hover proximityrange and then out of the first hover proximity range. In someembodiments, the device requires that finger 734 hovers within thesecond level hover proximity range for at least a threshold amount oftime before the cursor placement mode is ended and the selection resizemode is activated. In some embodiments, the device requires that finger734 hovers over cursor 1074 within the second level hover proximityrange for at least a threshold amount of time before the cursorplacement mode is ended and the selection resize mode is activated. Insome embodiments, once selection object 1082 is expanded, finger 734 canmove back out to the first level hover proximity range withoutdisturbing the selection, and reenter the second level hover proximityrange to reselect one of the two selection handles (e.g., by hoveringnear the selection handle, or hover and hold over the selection handlefor a threshold amount of time) and move the selected selection handleto resize the selection object. In some embodiments, when finger 734moves back out to the first level hover proximity range, magnifyingloupe 1088 ceases to be displayed, and when finger 734 reenters thesecond level hover proximity range and selects one of the selectionhandles, magnifying loupe 1088 is redisplayed near the selectedselection handle. In some embodiments, when finger 734 moves back out ofthe first level hover proximity range, selection object 1082 is removed(e.g., the selection is canceled) unless finger 734 makes contact withthe touch-screen first. In some embodiments, when finger 734 moves backout of the first level hover proximity range, selection object 1082remains displayed, and when finger 734 then moves back into the firstlevel hover proximity range, cursor placement mode is reentered with theselection object 1082 remaining on the touch-screen.

FIGS. 11A-11J illustrate hovering an input object over a first objectfor at least a threshold amount of time to enter a mode for performing arespective operation with respect to the first object (e.g., aninformation display mode for displaying tool tips or missednotifications for an object, such as a control affordance, or anapplication launch icon), and once the mode is entered, when the inputobject moves laterally over another object (e.g., an object of the sametype), the respective operation is performed with respect to the objectwithout requiring the input object to hover over the object for at leastthe threshold amount of time (e.g., the respective operation isperformed immediately). In some embodiments, the device requires theinput object to meet requirements other than the hover-hold timethreshold to enter the mode. For example, a predefined in-air gesture isrequired to enter the mode, and once the mode is entered, the devicedoes not require the in-air gesture to be performed again for the nextobject in order to perform an operation with respect to the next object.In some embodiments, the device requires the input object to enter thesecond level hover proximity range (e.g., be close to the touch-screen)to enter the mode, and once the mode is entered, the device only requirethe input object to be in the first-level hover proximity range in orderto perform an operation associated with the mode.

In FIG. 11A, home screen user interface 1102 is displayed. Within homescreen user interface 1102, a number of application launch icons aredisplayed, including some application launch icons with unreadnotifications or messages. For example, there are four unreadnotifications or messages for the telephone application (e.g., asindicated by the badge on the application launch icon 1106); there arefive unread notifications or messages for the mail application (e.g., asindicated by the badge on the application launch icon 1104), and thereare two unread notifications or messages for the instant messagingapplication.

In FIG. 11B, a new message for the mail application has arrived at thedevice, and a notification is generated (e.g., as represented bynotification banner 1108) and displayed over home screen user interface1102. If no user interaction with notification banner 1108 is detectedwithin a threshold amount of time since the initial display ofnotification banner 1108, notification banner 1108 ceases to bedisplayed (e.g., the notification may be stored in a notification centerfor the user to review later).

In FIGS. 11C-11D, finger 734 has moved toward the touch-screen andentered the hover proximity range above the touch-screen (e.g., finger734 moved to a hover location above application launch icon 1104 at timeto). Finger 734 is then held over application launch icon 1104 for themail application (e.g., indication 1110 for finger 734 is over the badgeportion of application launch icon 1104 in FIGS. 11C-11D). When finger734 is held over application launch icon 1104 for less than a thresholdamount of time T, no visible change is applied to application launchicon 1104 (e.g., as shown in FIG. 11C). When finger 734 is held overapplication launch icon 1104 for at least the threshold amount of timeT, application launch icon 1104 is highlighted, and the previouslydisplayed notification banner 1108 is redisplayed over home screen userinterface 1102. In some embodiments (not shown), notification banner1108 will remain displayed for a period of time without requiring finger734 to be continuously held over application launch icon 1104. If finger734 is lifted out of the hover proximity range, and taps on notificationbanner 1108 while it is still displayed, the mail application will belaunched. If finger 734 is lifted out of the hover proximity range, andno user interaction with notification banner 1108 is detected within athreshold amount of time, notification banner 1108 ceases to bedisplayed. Notification banner 1108 will remain displayed for as long asfinger 734 hovers over application launch icon 1104. In someembodiments, portions of home screen user interface 1102 outside of icon1104 are blurred and darkened underneath notification banner 1108.

FIGS. 11E-11F illustrate that, once notification banner 1108 isdisplayed, the device has entered an information display mode that willdisplaying information (e.g., missed notifications) for additionalobjects without requiring finger 734 to hold over the additional objectsfor the same threshold amount of time as for application launch icon1104. In some embodiments, the additional objects are of the same typeof the first object (e.g., application launch icon 1104) for which theinformation display mode was first activated, and the information thatis displayed for the additional objects are of the same type as theinformation (e.g., notification banner 1108) that was displayed for thefirst object (e.g., application launch icon 1104). As shown in FIG. 11E,while notification banner 1108 remains displayed over home screen userinterface 1102, finger 734 starts to move laterally toward applicationlaunch icon 1106 while remaining within the hover proximity range abovethe touch-screen. In FIG. 11F, as soon as finger 734 moves to a hoverlocation above application launch icon 1106 (as indicated by theposition of indication 1110 for finger 734), application launch icon1106 becomes highlighted and notification banner 1112 for the telephonyapplication is displayed. At the same time, application launch icon 1104ceases to be highlighted and notification banner 1108 ceases to bedisplayed.

FIG. 11G shows an embodiment in which, when finger 734 moves laterallyto application launch icon 1106 after the information display mode hasbeen entered, notification banner 1112 for application launch icon 1106is displayed, while notification banner 1108 for application launch icon1104 remains displayed over home screen user interface 1102. In someembodiments, both notification banner 1108 and notification banner 1112crease to be displayed when finger 734 is lifted out of the hoverproximity range above the touch-screen and the information display modeis exited.

FIG. 11H continues from FIG. 11F or 11G. FIG. 11H shows that, whenfinger 734 is lifted out of the hover proximity range above thetouch-screen, notification banner 1112 (and notification banner 1108)cease to be displayed (e.g., after a predefined period of time) and theinformation display mode is exited (e.g., immediately upon finger 734exiting the hover proximity range).

FIGS. 11I-11J illustrate that, after the information display mode hasbeen exited, in order to redisplay notification banner 1112, finger 734is required to reenter the hover proximity range and hover overapplication launch icon 1106 (e.g., as indicated by indication 1114 overapplication launch icon 1106) for at least the threshold amount of timeT. Once finger 734 has reentered the hover proximity range (e.g., finger734 reentered the hover proximity range above application launch icon1106 at time t3, as shown in FIG. 11I) and hovered over applicationlaunch icon 1106 for at least the threshold amount of time, theinformation display mode is reentered, and notification banner 1112 isredisplayed (e.g., at time t4, notification banner 1112 is redisplayed).

FIGS. 12A-12R illustrate using a hover input to distinguish userinterface objects that have differentiated object-specific responses tointensity-based inputs (e.g., a light press, a deep press input, e.g.,as opposed to non-intensity-based inputs such as a tap input, atouch-hold input) from user interface objects that do not havedifferentiated, object-specific responses to intensity-based inputs. Anintensity threshold that is above the contact-detection intensitythreshold is used as part of the criteria to detect and recognize anintensity-based input. A non-intensity-based input, such as a tap inputor a touch-hold input (e.g., a long press input) does not require thecontact to have an intensity that meets another intensity thresholdabove the contact-detection intensity threshold in order for the inputto be detected and recognized. A time threshold between touch-down andlift-off is sometimes used as part of the criteria to detect andrecognize a non-intensity-based input. An object that has differentiatedresponses for intensity-based inputs has a first response to a tap inputand a different response for a light press input with an intensityexceeding a light press intensity threshold, and optionally anotherdifferent response for a deep press input with an intensity exceedingthe deep press intensity threshold above the light press intensitythreshold. An object that does not have differentiated responses forintensity-based inputs has the same response for a tap input and a lightpress input with lift-off, for example.

In FIG. 12A, home screen user interface 1202 is displayed. Home screenuser interface 1202 includes a number of application launch iconscorresponding to different applications installed on the device. Someapplication launch icons (e.g., application launch icons 1204 and 1212)have corresponding application-specific quick action menus that aredisplayed when the application launch icons are activated by a contactwith an intensity that exceeds a light press intensity threshold IT_(L).Some other application launch icons (e.g., application launch icons 1210and 1216) do not have corresponding application-specific quick actionmenus, and do not display such menus or other associatedapplication-specific user interface objects when the application launchicons are activated by a contact with an intensity that exceeds thelight press intensity threshold IT_(L). A tap input on any of theapplication launch icons will cause the device to launch the applicationthat corresponds to the tapped application launch icon.

FIGS. 12B-12C illustrate that, when finger 734 enters the hoverproximity range above the touch-screen and while finger 734 hovers overapplication launch icon 1204 (as indicated by indication 1208 of finger734), preview platter 1206 merges from behind application launch icon1204 to indicate to the user that application launch icon 1204 hasdifferentiated, object-specific/application-specific responses tointensity-based inputs. In FIGS. 12B-12C, while finger 734 hovers overapplication launch icon 1204, portions of home screen user interface1202 that are outside of application launch icon 1204 are darkened andblurred. In some embodiments, the amount of darkening and blurringapplied to home screen user interface 1202 and the appearance of previewplatter 1206 are dynamically changed in accordance with a current valueof the hover proximity parameter (e.g., hover distance 514) of finger734. For example, when finger 734 hovers closer to the touch-screen,preview platter 1206 grows in size, and home screen user interface 1202becomes increasingly darkened and blurred. The visual effects (e.g., thepreview platter and the darkening and blurring of the home screen userinterface) are removed if finger 734 is lifted out of the hoverproximity range or moved over to another application launch icon thatdoes not have differentiated, object-specific responses tointensity-based inputs.

FIGS. 12D-12E illustrate that, when finger 734 moves laterally toanother hover location over application launch icon 1210 that does nothave differentiated, object-specific responses to intensity-basedinputs, the appearance of application launch icon 1210 is changed toindicate that finger 734 is now hovering over application launch icon1210 (as indicated by indication 1208 of finger 734, and highlighting ofapplication launch icon 1210), but no preview platter merges from behindapplication launch icon 1210 and no darkening and blurring of homescreen user interface 1202 are applied. In some embodiments, thehighlighting of application launch icon 1210 remains unchanged when thecurrent value of the hover proximity parameter (e.g., hover distance514) of finger 734 changes (e.g., application launch icon 1210 looks thesame in FIGS. 12D and 12E).

FIG. 12F shows that, when finger 734 hovers over another applicationlaunch icon 1212 (e.g., as indicated by indication 1208 of finger 734)that has differentiated, object-specific responses to intensity-basedinputs, preview platter 1214 emerges from behind application launch icon1212. The appearance and behavior of preview platter 1214 are optionallyidentical to the appearance and behavior of preview platter 1206 forapplication launch icon 1204. Similarly, home screen user interface 1202is darkened and blurred in the same manner as shown in FIG. 12B.

FIG. 12G shows that, when finger 734 hovers over another applicationlaunch icon 1216 (e.g., as indicated by indication 1208) that does nothave differentiated, object-specific responses to intensity-basedinputs, application-launch icon 1216 is highlighted. The highlightingthat is applied to application-launch icon 1216 is consistent, similar,and optionally identical to the highlighting that is applied toapplication-launch icon 1210 in FIG. 12D.

FIGS. 12H-12I continue from 12E. After finger 734 hovers overapplication launch icon 1210, finger 734 makes contact with applicationlaunch icon 1210 (e.g., as indicated by contact 1220). When theintensity of contact 1220 increases and exceeds the light pressintensity threshold IT_(L) (as indicated by intensity meter 1201), acanned visual effect is shown to indicate that a light press input hasbeen detected, but that application launch icon 1210 does not have anobject-specific response to the light press input. As shown in FIG. 12H,a hint 1222 of a preview platter emerges from behind application launchicon 1210 and tactile output 1224 (e.g., a “failure” haptic) isgenerated, when the light press input is detected. The hint 1222 of thepreview platter fades away quickly during the canned visual effect. FIG.12I shows that, the canned visual effect is completed, and finger 734 islifted off the touch-screen. While finger 734 hovers over applicationlaunch icon 1210 (as indicated by indication 1226), the samehighlighting is applied to application launch icon 1210 to indicate thatit does not have differentiated, object-specific response tointensity-based inputs, and only have a canned, generic response (whichhas been illustrated in FIG. 12H).

In FIGS. 12J-12L, finger 734 moves laterally to a hover location overapplication launch icon 1204 again. The same visual effects shown inFIG. 12C are redisplayed. In FIG. 12K, finger 734 makes contact withapplication launch icon 1204 (e.g., as indicated by contact 1226). Whenthe intensity of contact 1226 increases, preview platter 1206 grows insize and shifts relative to application launch icon 1204, and userinterface 1202 is darkened and blurred further (as shown in FIG. 12K).Once the intensity of contact 1226 exceeds the light press intensitythreshold, preview platter 1206 transforms into mini application object1228 and quick action menu 1230 that correspond to the messagesapplication (as shown in FIG. 12L). The amount of blurring and darkeningapplied to user interface 1202 is at their maximum extent. A tactileoutput (e.g., tactile output 1232) is generated when the light pressinput is detected and the quick action menu and mini application objectare displayed.

FIGS. 12M-12O illustrate that, when finger 734 lifts up from thetouch-screen after mini application object 1228 and quick action menu1230 have been displayed in response to the light press input by contact1226, the appearances of mini application object 1228 and quick actionmenu 1230 are altered in accordance with a current value of the hoverproximity parameter of finger 734, e.g., becoming increasinglytranslucent with increasing hover distance 514 above the touch-screen.In addition, the amount of blurring and darkening of home screen userinterface 1202 is also decreased with increasing hover distance 514above the touch-screen. FIGS. 12M-12O also illustrate that, after finger734 is lifted off the touch-screen, finger 734 moves laterally whileremaining within the hover proximity range above the touch-screen (asindicated by indication 1238), and as long as finger 734 is stilldetected within the hover proximity range above the touch-screen,display of mini application object 1228 and quick action menu 1230 ismaintained.

FIG. 12P continues from FIG. 12O. FIG. 12P illustrates that, if finger734 is lifted out of the hover proximity range without first makingcontact with the touch-screen again, mini application object 1228 andquick action menu 1230 cease to be displayed, and home screen userinterface 1202 is restored to its original appearance.

FIGS. 12Q-12R continues from 12O. In contrast to the scenario shown inFIG. 12P, finger 734 makes contact with the touch-screen at a locationthat corresponds to one of the selectable options in quick action menu1230 (as indicated by contact 1234). Upon lift-off of contact 1234, theselectable option that is touched by contact 1234 is activated, and theinstant messaging application that corresponds to application launchicon 1204 is launched and user interface 1236 that corresponds to theselectable option is displayed (as shown in FIG. 12R).

FIGS. 13A-13N illustrate visually indicating which selection handleamong multiple selection handles of a content selection object isselected for movement when an input object hovers over the selectionhandle, in accordance with some embodiments.

In FIG. 13A, content display user interface 1302 (e.g., a user interfaceof a text editor application or a user interface of a web browserapplication, etc.) displays selectable content (e.g., text). A portionof the displayed content has been selected. The selection is enclosed ina selection object (e.g., selection object 1304 with two selectionhandles, including start selection handle 1306 and end selection handle1308). The selection of the text is optionally carried out in a mannerthat is described with respect to FIGS. 10T-10Y, or other conventionaltext selection methods.

FIGS. 13B-13C illustrate that, when finger 734 moves toward thetouch-screen and enters the hover proximity range, and if (x,y) position504 of finger 734 is over one of the selection handles (e.g., selectionhandle 1308) (e.g., as indicated by indication 1314 of finger 734) forat least a threshold amount of time T, the selection handle (e.g.,selection handle 1308) is highlighted relative to the other selectionhandle (e.g., selection handle 1306). For example, the end portion ofselection handle 1308 is enlarged relative to the corresponding endportion of selection handle 1306 to indicate that selection handle 1308has been selected for movement. In some embodiments, magnifying loupe1310 is displayed near the selected selection handle 1308. In someembodiments, magnifying loupe 1310 is only displayed after finger 734has hovered over selection handle 1308 for at least the threshold amountof time T. The magnifying loupe includes a magnified version of aportion of text surrounding selection handle 1308. Selection handle 1308is represented as cursor 1312 within the magnified text insidemagnifying loupe 1310.

FIGS. 13D-13G illustrate relocation of the selected selection handle1308 by movement of a continuously maintained contact. FIG. 13Dcontinues from FIG. 13C in some embodiments. In some embodiments, FIG.13D continues from FIG. 13B. When finger 734 moves closer to thetouch-screen and makes contact with the touch-screen (e.g., as indicatedby intensity meter 1301) at a location that corresponds to the selectedselection handle 1308 (e.g., as indicated by contact 1316), theappearance of selection handle 1308 is optionally changed to indicatethat contact has been made with selection handle 1308 (as shown in FIG.13D). When contact 1316 moves across the touch-screen, selection handle1308 is dragged by contact 1316 to expand the selection enclosed inselection object 1304. Magnifying loupe 1310 moves with selection handle1308 and the text shown in magnifying loupe 1310 is continuously updatedin accordance with the position of selection handle 1308 within the text(as shown in FIG. 13E). In FIG. 13F, finger 734 is lifted off thetouch-screen, and selection handle 1308 remains highlighted (e.g., inthe same manner as shown in FIG. 12C) while finger 734 continues tohover above selection handle 1308. If finger 734 moves laterally toanother hover location over selection handle 1306 instead (not shown),selection handle 1308 will be restored to its original appearance, andselection handle 1306 would be highlighted relative to selection handle1308 to indicate that selection handle 1306 is now selected formovement. In addition, magnifying loupe 1310 would be moved (not shown)to be near selection handle 1306 and showing text surrounding selectionhandle 1306. In FIG. 13G, once finger 734 is lifted out of the hoverproximity range above the touch-screen, the previously highlightedselection handle (e.g., selection handle 1308) is restored to itsoriginal appearance but remains at the new location, and the resizing ofthe selection object is completed.

FIGS. 13H-13J illustrate a scenario in which finger 734 is not held overa selection handle for more than the threshold amount of time T beforefinger 734 makes contact with the touch-screen. When the contact movesacross the touch-screen, content display user interface 1302 isscrolled. In FIG. 13H, finger 734 is at a hover location over selectionhandle 1308 (as indicated by indication 1318 of finger 734) (e.g., whenfinger 734 is on its way to make contact with the touch-screen). Beforefinger 734 hovers over selection handle 1308 for at least the thresholdamount of time T, the selection object does not change in appearance.After finger 734 makes contact with the touch-screen (e.g., as indicatedwith contact 1320), the entire content display user interface 1302scrolls with movement of contact 1320 across the touch-screen (as shownin FIGS. 13I-13J). Although content selection object 1304 is displayedon content display user interface, scrolling of user interface 1302 bycontact 1320 does not require the presence of content selection object.In addition, the scrolling of the user interface does not require thecontact to be located on or near a selection handle, and may beperformed by a contact on any part of the displayed content.

FIG. 13K continues from FIG. 13D. FIG. 13K illustrates that, selectionhandle 1308 is moved in accordance with lateral movement of finger 734while finger 734 remains with the hover proximity range above thetouch-screen.

FIG. 13L follows FIG. 13K and illustrates that, if finger 734 is liftedout of the hover proximity range without first making contact with thetouch-screen again, selection handle 1308 is restored to its originallocation and the resizing of the selection object 1304 is canceled.

FIGS. 13M-13N follows FIG. 13K and illustrates that, if finger 734 islifted out of the hover proximity range after making contact with thetouch-screen (e.g., as indicated by contact 1322) again, selectionhandle 1308 remains at its new location in the text. Additional detailsof this behavior is described with respect to FIGS. 8P and 8V, forexample.

FIGS. 14A-14M illustrate operation of a reactive region for maintaininginput focus on an object, where the reactive region has differentlateral ranges at different hover distances above the touch-screen, inaccordance with some embodiments.

FIG. 14A shows a user interface (e.g., map user interface 1402) thatincludes a plurality of user interface objects (e.g., location pin 1404and location pin 1406) that are selectable when finger 734 hovers abovethem. The (x,y) position 1408 of location pin 1404 is indicated ontouch-screen 112.

FIGS. 14B-14C illustrate that, when finger 734 moves toward thetouch-screen and enters the hover proximity range above a region thatdoes not have any selectable objects (e.g., as indicated by indication1410 in FIG. 14C), an empty information pop-up (e.g., pop-up 1412) isdisplayed at the location that corresponds to the (x,y) position 504 offinger 734.

FIG. 14D illustrates that, when finger 734 moves to a hover locationthat is directly above location pin 1404 (e.g., with (x,y) position 504of finger 734 within a narrow lateral range around position 1408), inputfocus is shifted to location pin 1404 and information pop-up 1414 thatcorresponds to location pin 1404 is displayed.

FIGS. 14E-14F illustrate a reactive region of location pin 1404 that iswider closer to the touch-screen and narrower farther away from thetouch-screen (e.g., as represented by the boundary line 1418 of thereactive region, where the reactive region is inside a cone defined byboundary line 1418 (only half of the cone is shown in the figures)).FIG. 14E shows that, once input focus is shifted to location pin 1404(after finger 734 has met the stringent requirement for shifting inputfocus onto location pin 1404), input focus does not shift away fromlocation pin 1404 when finger 734 is no longer directly above locationpin 1404 (e.g., with (x,y) position 504 of finger 734 outside of thenarrow lateral range around position 1408). FIGS. 14E-14F show that, asfinger 734 moves laterally away from location pin 1404, as long asfinger 734 remains within the reactive region defined by boundary line1418, input focus would remain with location pin 1404 and informationpop-up 1414 would remain displayed. It is to be noted that althoughboundary line 1418 is shown to be straight, it does not need to bestraight in some embodiments. In some embodiments, the lateral range ofthe reactive region is calculated on the fly based on various factorsincluding the hover proximity parameter of finger 734 and optionally thespeed and direction of finger 734 at the moment, therefore, the reactiveregion is not a predefined region with fixed shape, but rather isdynamically determined during the hover movement of finger 734. Inaddition, in some embodiments, the lateral range of the reactive regionmay increase with increasing hover distances for a first range of hoverdistances and may decrease with increasing hover distances for secondrange of hover distances (e.g., that are above the first range, or thatare below the first range).

FIG. 14G illustrates that, finger 734 is moved outside of the reactiveregion defined by boundary 1418, input focus is taken away from locationpin 1404 and information pop-up 1414 is replaced with the emptyinformation pop-up 1410.

FIGS. 14H-14I illustrate that, when finger 734 is outside of thereactive region of location pin 1404, and then hovered directly overlocation pin 1404 again, input focus is placed on location pin 1404 andinformation pop-up 1414 is displayed again.

FIG. 14J shows that, when finger 734 is moved laterally at a higherhover distance from the touch-screen (as compared to the cases shown inFIG. 14F), input focus is taken away from location pin 1404 when finger734 is moved by a smaller lateral distance from the location 1408 thanthat shown in FIGS. 14F-14G, because the threshold lateral range forshifting input focus away from location pin 1404 is smaller at thehigher hover distance above the touch-screen.

FIG. 14K illustrates that, when finger 734 hovered over location pin1404 again, input focus is placed on location pin 1404 and informationpop-up 1414 is displayed again. If finger 734 moves toward thetouch-screen with a speed greater than a threshold speed, input focus ismaintained on location pin 1404 for at least a threshold amount of time,even if finger 734 is outside of the reactive region of location pin1404 during its journey to the touch-screen. For example, as shown inFIG. 14L, the input focus is maintained on location pin 1404 when finger734 makes contact with the touch-screen within the threshold amount oftime, even though finger 734 has made contact (e.g., as indicated bycontact 1420) with the touch-screen outside of the reactive region oflocation pin 734. FIG. 14M shows that, when lift-off of contact 1420 isdetected, additional information related to location pin 1404 isdisplayed, e.g., in information platter 1422.

FIGS. 15A-15C are flow diagrams illustrating a method 1500 ofinteracting with a user interface object through proximity-based andcontact-based inputs in accordance with some embodiments. The method1500 is performed at an electronic device (e.g., device 300, FIG. 3, orportable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the electronic deviceincludes one or more first sensors to detect proximity of an inputobject (e.g., a finger or a stylus) above the touch-sensitive surface(e.g., proximity sensors (such as infrared sensors), capacitive sensorsin the touch sensitive surface, or cameras next to the touch-sensitivesurface) and one or more second sensors to detect intensities of contactof the input object with the touch-sensitive surface. In someembodiments, the one or more second sensors are different from the oneor more first sensors. In some embodiments, the one or more secondsensors are the same as the one or more first sensors. In someembodiments, the touch-sensitive surface and the display are integratedinto a touch-sensitive display. In some embodiments, the display is atouch-screen display and the touch-sensitive surface is on or integratedwith the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 1500 are, optionally,combined and/or the order of some operations is, optionally, changed.

As described below, the method 1500 provides an intuitive way tointeract with a user interface object through proximity-based andcontact-based inputs. In particular, by dynamically varying a visualcharacteristic of a selected user interface object in accordance withthe current hover proximity parameter of the input object while of theuser interface object is dragged by the input object, the deviceprovides visual feedback to the user regarding the user's input, suchthat the user can timely adjust the input (e.g., the hover proximityparameter) to avoid input mistakes (e.g., accidentally dropping theobject by moving too close or too far away from the touch-sensitivesurface) and accomplish an intended operation more efficiently (e.g., bytimely dropping the object at a desired location or continuing to movethe object toward an intended destination). The method reduces thenumber, extent, and/or nature of the inputs from a user when interactingwith a user interface object, thereby creating a more efficienthuman-machine interface. For battery-operated electronic devices,enabling a user to reposition an object faster and more efficientlyconserves power and increases the time between battery charges.

The device displays (1502) a user interface object (e.g., user interfaceobject 704) at a first location on the display (e.g., as shown in FIG.7A).

The device detects (1504) selection of the user interface object at thefirst location on the display (e.g., the user interface object isselected in response to a hover input, a tap input, or a press inputdirected to the user interface object).

While the user interface object is selected (1506), the device detectslateral movement of the input object (e.g., a finger or a stylus) overthe touch-sensitive surface while the input object meets hover criteria(e.g., the hover criteria require that a hover proximity parameter(e.g., a parameter based on hover distance) associated with the inputobject is less than a threshold proximity value (e.g., a threshold hoverdistance) in order for the hover criteria to be met); and, in responseto detecting lateral movement of the input object over thetouch-sensitive surface while the input object meets the hover criteria:the device moves the selected user interface object (e.g., from thefirst location to a second location on the display) in accordance withthe lateral movement of the input object over the touch-sensitivesurface; and, while moving the selected user interface object inaccordance with the lateral movement of the input object over thetouch-sensitive surface, the device dynamically varies a first visualcharacteristic (e.g., size, color saturation, transparency, perceiveddepth relative to the surface of the display, etc.) of the selected userinterface object in accordance with a current hover proximity parameterof the input object. For example, as shown in FIGS. 7L-7R, after object704 is lifted up by stylus 203, the size of object 704 is dynamicallyvaried in accordance with hover distance 514 of stylus 203 duringlateral movement of stylus 203, while stylus 203 remains within thethreshold hover distance above touch-sensitive surface 651.

In some embodiments, the hover criteria include (1508) a criterion thatis met when the hover proximity parameter of the input object is lessthan a threshold proximity value. For example, the detected distance ofa fingertip above the touch-sensitive surface is less than a thresholddistance. As used in the specification and claims, the term “hoverproximity parameter” refers to the (non-zero) distance of the inputobject above the touch-sensitive surface or to a substitute (proxy) forthe distance of the input object above the touch-sensitive surface. Insome embodiments, a change in capacitance detected on thetouch-sensitive surface due to changing distance of an input objectabove the touch-sensitive surface is a proxy for the distance of theinput object above the touch-sensitive surface. In some embodiments, thehover criteria include a criterion that the input object is not touchingthe touch-sensitive surface.

In some embodiments, while the input object is detected, the devicedisplays (1510) a position indicator (e.g., a cursor, an image of afingertip or hand, an image representing a shadow cast by the inputobject, an icon representing a focus selector, an icon representing aselection tool, etc.) (e.g., indicator 706) at a location on the displaythat corresponds to a current position (e.g., (x,y) position 504 ofstylus 203) of the input object over the touch-sensitive surface. Insome embodiments, the location on the display that corresponds to thecurrent position of the input object lies directly below the inputobject. In some embodiments, the location on the display thatcorresponds to the current position of the input object does notnecessarily lie directly below the input object, and may be offsetlaterally from the position that is directly below the input object(e.g., position 701 is offset from (x,y) position 504 of stylus 203).For example, the location on the display that corresponds to the currentposition of the input object may be a projection of the tip of the inputobject onto the display surface in accordance with the current azimuthaland inclination angles of the input object. In another example, a fingerhovering over the touch-screen causes a position indicator (also servingas the focus selector) to be displayed at a position on the touch-screenthat is offset upward by a distance such that the finger does notobscure the user's view of the focus selector. By offsetting theposition of the position indicator from the (x,y) position of thefingertip, the user is able to better control the movement and positionof the position indicator and manipulate objects with better precisionand fewer mistakes.

In some embodiments, the device (dynamically) varies (1512) a visualcharacteristic of the position indicator (e.g., size, color saturation,transparency, and/or 3D visual effect such as a shadow shape and/orlength) in accordance with the current hover proximity parameter of theinput object (e.g., dynamically changing (e.g., increasing ordecreasing) a size or transparency of the position indicator as thedetected (non-zero) hover distance of the input object above thetouch-sensitive surface changes (e.g., increases or decreases, or viceversa)). For example, the device dynamically varies the size ofindicator 706 in accordance with the hover distance 514 during movementof stylus 203, as shown in FIGS. 7L-7R. In some embodiments, when theinput object is well within the hover distance from the touch-sensitivesurface, the position indicator has a “normal” appearance (e.g., aneutral color or normal opaqueness); and when the input object isgetting very close to the touch-sensitive surface and contact with thetouch-sensitive surface is imminent, the position indicator takes on afirst “warning” appearance (e.g., an orange alert color and/or completeopaqueness); and when the input object is getting very close to theproximity threshold, and termination of hover interaction is imminent,the position indicator takes on a second “warning” appearance (e.g., ared alert color and/or near complete transparency). This is illustratedin FIG. 7Q (e.g., by flickering edge 712 of indicator 706). In someembodiments, by (dynamically) varying a visual characteristic of theposition indicator in accordance with the current hover proximityparameter of the input object (e.g., before election of the userinterface object, while the user interface object is dragged by theinput object, and/or after the object is dropped off), the deviceprovides visual feedback to the user regarding the current state user'sinput (e.g., function currently performed or function that can beactivated by the current input), such that the user can timely adjustthe input (e.g., adjusting the hover proximity parameter) to avoid inputmistakes (e.g., accidentally picking up or dropping off the object bymoving too close or too far away from the touch-sensitive surface) andaccomplish an intended operation more efficiently (e.g., by timelypicking up the desired object, or dropping the object off at a desiredlocation, or continuing to move the object toward an intendeddestination).

In some embodiments, detecting selection of the user interface objectincludes (1514) detecting the input object making and breaking contactwith the touch-sensitive surface at a location that corresponds to thefirst location of the user interface object on the display (e.g.,detecting a tap gesture, or a long press gesture by the input object ata location that corresponds to the user interface object). In someembodiments, upon lift-off of the input object, the user interfaceobject is selected; and upon selection of the user interface object, theposition indicator of the input object changes appearance as well (e.g.,a hand indicator changes from an open palm to a closed fist). This isillustrated in FIGS. 7J-7M, for example.

In some embodiments, detecting selection of the user interface objectincludes (1516) detecting a press input by the input object at alocation that corresponds to the first location of the user interfaceobject on the display, wherein detecting the press input includesdetecting a characteristic intensity of a contact of the input objectwith the touch-sensitive surface above a first threshold intensity(e.g., a light press or deep press intensity threshold). In someembodiments, the user interface object is selected when liftoff isdetected after the first threshold intensity is met by the input object,or immediately upon the input object meeting the first thresholdintensity; and upon selection of the user interface object, the positionindicator of the input object changes appearance as well (e.g., a handindicator changes from an open palm to a closed fist). In someembodiments, when a press input is required for selecting the object, aninput by a contact that does not meet the first intensity thresholdoptionally triggers an operation associated with the object. Forexample, when the object is a weather item, a tap input triggers displayof a user interface that includes more information about the weatheritem, and a press input that meets the first threshold intensity selectsthe weather item. In another example, where the object is a calendarentry, a tap input triggers display of a user interface that includesmore information about the calendar, and a press input that meets thefirst threshold intensity selects the calendar item. By requiring thecharacteristic intensity of the contact to increase above the firstthreshold intensity in order to select the user interface object, thedevice reduces user mistakes (e.g., accidental selection of the objectwhile hovering above the touch-sensitive surface may be avoided), andimproves operability of the device (e.g., precise control of the inputobject above the touch-sensitive surface is not mandated).

In some embodiments, detecting selection of the user interface objectincludes (1518) detecting a long press input by the input object at alocation that corresponds to the first location of the user interfaceobject on the display, wherein detecting the long press input includesdetecting a characteristic intensity of a contact of the input objectwith the touch-sensitive surface remains above a first thresholdintensity for at least a threshold amount of time. This is illustratedin FIGS. 7K-7L. In some embodiments, when a long press input is requiredfor selecting the object, an input by a contact that does not meet thefirst intensity threshold or the time threshold optionally triggers anoperation associated with the object or triggers display of additionalinformation related to the object. For example, when the object is anapplication launch icon, a tap input triggers launches an applicationassociated with the application launch icon, a press input causesdisplay of a quick action menu with selectable options to activaterespective operations associated with the application, and a long pressinput causes selection of the application launch icon. By requiring thecharacteristic intensity of the contact to increase above the firstthreshold intensity and be maintained for at least a threshold amount oftime in order to select the user interface object, the device reducesuser mistakes (e.g., accidental selection of the object while hoveringabove the touch-sensitive surface may be avoided), and improvesoperability of the device (e.g., precise control of the input objectabove the touch-sensitive surface is not mandated).

In some embodiments, prior to detecting selection of the user interfaceobject at the first location (e.g., before a tap gesture, a long pressinput, or a press input with the input object selects the user interfaceobject as the target of a “hovering drag” gesture) and while the inputobject meets the hover criteria (1520): the device detects the inputobject over a location on the touch-sensitive surface that correspondsto the first location of the user interface object on the display; and,while detecting the input object over the location on thetouch-sensitive surface that corresponds to the first location of theuser interface object on the display, the device (dynamically) varies anappearance of the user interface object at the first location inaccordance with the current hover proximity parameter of the inputobject (e.g., dynamically changing a size and/or color of the unselecteduser interface object as the detected (non-zero) hover distance of theinput object above the touch-sensitive surface changes) (as illustratedin FIGS. 7C-7E); while (dynamically) varying the appearance of the userinterface object at the first location, the device detects lateralmovement of the input object over the touch-sensitive surface (e.g.,lateral movement that goes beyond the immediate vicinity (e.g., athreshold lateral range) above the unselected user interface object);and, in response to detecting lateral movement of the input object overthe touch-sensitive surface: the device ceases to (dynamically) vary theappearance of the user interface object at the first location; and, thedevice maintains the user interface object at the first location (e.g.,as shown in FIG. 7I, where lateral and vertical movements of stylus 203cease to influence object 704). In some embodiments, the image of theunselected user interface object is skewed (e.g., dynamically stretchedwhile remaining anchored at its original location) with small lateralmovements of the input object when the input object varies its lateralposition while hovering above the unselected user interface object(e.g., as shown in FIGS. 7F-7I). In some embodiments, by providingvisual feedback to the user regarding interactions with the object(e.g., lateral movement by input object near the object) prior toselection of the object (e.g., prior to the input object meetingselection criteria), the device helps the user to timely adjust theinput (e.g., the hover proximity parameter) to avoid input mistakes(e.g., accidentally selecting the object by moving too close to thetouch-sensitive surface, or accidentally selecting the wrong object whenmoving too close to the wrong object among several closely positionedobjects) and accomplish an intended operation more efficiently (e.g., byadjusting the direction of movement toward a desired target andadjusting the hover proximity parameter at a desired location).

In some embodiments, in response to detecting selection of the userinterface object at the first location on the display, the deviceprovides (1522) visual feedback to indicate that the user interfaceobject is selected (e.g., displaying an animation showing that the userinterface object is “picked up” by the hovering input object, showingshimmers of the user interface object to indicate the activated state ofthe user interface object, or casting a shadow under the selected userinterface object to indicate that the user interface object is nowhovering above its original plane) (e.g., the position indicator of theinput object changes its appearance to indicate that the object isselected (e.g., the position indicator changes its appearance from anopen palm to a closed fist)). This is illustrated in FIG. 7L.

In some embodiments, dynamically varying the first visual characteristicof the user interface object in accordance with the current hoverproximity parameter of the input object includes (1524) dynamicallychanging a size of the user interface object in accordance with thecurrent hover proximity parameter of the input object (e.g., dynamicallychanging the size of the selected user interface object as the detected(non-zero) hover distance of the input object above the touch-sensitivesurface changes). In some embodiments, the user interface objectincreases in size as the distance between the input object and thedisplay (or touch-sensitive surface) increases (e.g., the user interfaceobject is being lifted with the finger or stylus). This is illustratedin FIGS. 7L-7R, for example. In some embodiments, the user interfaceobject decreases in size as the distance between the input object andthe display increases (e.g., the user interface object is graduallyfalling away from the finger). In some embodiments, by (dynamically)varying the size of the user interface object in accordance with thecurrent hover proximity parameter of the input object, while the userinterface object is dragged by the input object, the device providesvisual feedback to the user regarding the current state user's input,such that the user can timely adjust the input (e.g., adjusting thehover proximity parameter) to avoid input mistakes (e.g., accidentallydropping off the object by moving too close to the touch-sensitivesurface) and accomplish an intended operation more efficiently (e.g., bytimely dropping the object off at a desired location, or continuing tomove the object toward an intended destination).

It should be understood that the particular order in which theoperations in FIGS. 15A-15C have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 1600, 1700, 1800, 1900, 2000, 2100, 2200, 2300 and 2400) arealso applicable in an analogous manner to method 1500 described abovewith respect to FIGS. 15A-15C. For example, the contacts, gestures,input objects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described above with reference to method 1500 optionally haveone or more of the characteristics of the contacts, gestures, inputobjects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described herein with reference to other methods describedherein (e.g., methods 1600, 1700, 1800, 1900, 2000, 2100, 2200, 2300 and2400). For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 15A-15C are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, detection operations and feedback operations 1504, 1506, and1520 are, optionally, implemented by event sorter 170, event recognizer180, and event handler 190. Event monitor 171 in event sorter 170detects a contact on touch-sensitive display 112, and event dispatchermodule 174 delivers the event information to application 136-1. Arespective event recognizer 180 of application 136-1 compares the eventinformation to respective event definitions 186, and determines whethera first contact at a first location on the touch-sensitive surfacecorresponds to a predefined event or sub-event, such as selection of anobject on a user interface. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally utilizes or calls data updater 176 or objectupdater 177 to update the application internal state 192. In someembodiments, event handler 190 accesses a respective GUI updater 178 toupdate what is displayed by the application. Similarly, it would beclear to a person having ordinary skill in the art how other processescan be implemented based on the components depicted in FIGS. 1A-1B.

FIGS. 16A-16E are flow diagrams illustrating a method 1600 ofinteracting with a user interface object through proximity-based andcontact-based inputs in accordance with some embodiments. The method1600 is performed at an electronic device (e.g., device 300, FIG. 3, orportable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the device includes one ormore first sensors to detect proximity of an input object above thetouch-sensitive surface (e.g., proximity sensors (such as infraredsensors), capacitive sensors in the touch sensitive surface, or camerasnext to the touch-sensitive surface) and one or more second sensors todetect intensity of contact of the input object with the touch-sensitivesurface In some embodiments, the one or more second sensors aredifferent from the one or more first sensors. In some embodiments, theone or more second sensors are the same as the one or more firstsensors. In some embodiments, the touch-sensitive surface and thedisplay are integrated into a touch-sensitive display. In someembodiments, the display is a touch-screen display and thetouch-sensitive surface is on or integrated with the display. In someembodiments, the display is separate from the touch-sensitive surface.Some operations in method 1600 are, optionally, combined and/or theorder of some operations is, optionally, changed.

As described below, the method 1600 provides an intuitive way tointeract with a user interface object through proximity-based inputs andcontact-based inputs. In some embodiments, by providing distinguishablevisual feedback regarding whether the object is responding to a hoverportion or a press portion of an input, the device provides a moreresponsive user interface and allows the user to timely adjust his/herinput to accomplish an intended task (e.g., to continue pushing towardthe touch-sensitive surface to make contact with the object) and/or toavert input mistakes (e.g., to stop pressing harder to avoid meeting anintensity threshold to trigger an unintended action). The moreresponsive user interface also helps to avoid causing user confusionduring an input because each portion of the input has a direct andimmediate impact on the visual appearance of the user interface. Themethod reduces the number, extent, and/or nature of the inputs from auser when interacting with a user interface object, thereby creating amore efficient human-machine interface. For battery-operated electronicdevices, enabling a user to interact with a user interface object fasterand more efficiently (e.g., by reducing user mistakes with improvedvisual feedback) conserves power and increases the time between batterycharges.

The device displays (1602) a user interface object (e.g., user interfaceobject 704) at a first location on the display, e.g., as shown in FIG.7U.

While displaying the user interface object at the first location on thedisplay, the device detects (1604) a first portion of an input by aninput object (e.g., a fingertip or a stylus), wherein detecting thefirst portion of the input includes detecting the input object at alocation over the touch-sensitive surface that corresponds to the firstlocation of the user interface object on the display while the inputobject meets hover criteria. For example, while the user interfaceobject is displayed, the device detects that a finger approaches theuser interface object from above touch-sensitive surface without makingcontact with the touch-sensitive surface, while a hover proximityparameter of the input object is less than a threshold distance abovethe touch-sensitive surface (e.g., while the input object remains withina threshold distance above the touch-sensitive surface without makingcontact with the touch-sensitive surface). This is shown in FIG. 7V, forexample.

In response to detecting the first portion of the input, the devicedynamically changes (1606) an appearance of the user interface object ina first manner in accordance with a current hover proximity parameter ofthe input object (e.g., the appearance of the user interface object isdynamically varied as the hover distance of the input object changes).For example, in some embodiments, while hover criteria are met andbefore the input object makes contact with the touch-sensitive surface,the size of the user interface object increases when the input objectapproaches the touch-sensitive surface, and decreases when the inputobject retreats from the touch-sensitive surface. This is shown in FIGS.7V-7X, for example. In another example, in some embodiments, while hovercriteria are met and before the input object makes contact with thetouch-sensitive surface, the color of the user interface object getsdarker when the input object approaches the touch-sensitive surface, andgets lighter when the input object retreats from the touch-sensitivesurface.

After dynamically changing the appearance of the user interface objectin a first manner in accordance with the current hover proximityparameter of the input object, the device detects (1608) a secondportion of the input by the input object, wherein detecting the secondportion of the input includes detecting the input object making contactwith the touch-sensitive surface at an initial contact location thatcorresponds to the first location on the display. This is shown in FIG.7Y, for example.

In response to detecting the second portion of the input, the devicedynamically changes (1610) the appearance of the user interface objectin a second manner in accordance with a current intensity of a contactby the input object on the touch-sensitive surface (e.g., while theinput object is in contact with the touch-sensitive surface, theappearance of the user interface object is dynamically varied inaccordance with the changing force or pressure of the input object onthe touch-sensitive surface). In some embodiments, the second manner ofchanging the appearance involves changing the same property of the userinterface object (e.g., size or color) as the first manner, but basingthe change on a different input parameter or metric from that used inthe first manner (e.g., value of the property (e.g., size) increaseswith increasing hover proximity parameter in the first portion of theinput, and value of the property (e.g., size) increases with increasingcontact intensity in the second portion of the input). In someembodiments, the second manner and second manner of changing theappearance involves changing two different properties of the userinterface object (e.g., varying the size with hover proximity parameterin the first portion of the input, and varying the color with contactintensity in the second portion of the input). In FIGS. 7Z-7AE, thedevice dynamically varies the size of object 704 with changing intensityof the contact of stylus 203 with touch-sensitive surface 651.

In some embodiments, the hover criteria require (1612) the hoverproximity parameter of the input object to be less than a thresholdproximity value in order for the hover criteria to be met. For example,the detected distance of a fingertip above the touch-sensitive surfaceis less than a threshold distance. As used in the specification andclaims, the term “hover proximity parameter” refers to the (non-zero)distance of the input object above the touch-sensitive surface or to asubstitute (proxy) for the distance of the input object above thetouch-sensitive surface. In some embodiments, a change in capacitancedetected on the touch-sensitive surface due to changing distance of aninput object above the touch-sensitive surface is a proxy for thedistance of the input object above the touch-sensitive surface. In someembodiments, the hover criteria include a criterion that the inputobject is not touching the touch-sensitive surface.

In some embodiments, while the input object is detected, the devicedisplays (1614) a position indicator (e.g., a cursor, an image of afingertip or hand, an image representing a shadow cast by the inputobject, an icon representing a focus selector, an icon representing aselection tool, etc.) (e.g., indicator 706 in FIG. 7V) at a location onthe display that corresponds to a current position of the input objectover or on the touch-sensitive surface. In some embodiments, thelocation on the display that corresponds to the current position of theinput object lies directly below the input object. In some embodiments,the location on the display that corresponds to the current position ofthe input object does not necessarily lie directly below the inputobject, and may be offset laterally from the position that is directlybelow the input object. For example, the location on the display thatcorresponds to the current position of the input object may be aprojection of the tip of the input object onto the display surface inaccordance with the current azimuthal and inclination angles of theinput object.

In some embodiments, the device (dynamically) varies (1616) a visualcharacteristic (e.g., size, color saturation, transparency, and/or 3Dvisual effect such as a shadow shape and/or length) of the positionindicator in accordance with the current hover proximity parameter ofthe input object (e.g., dynamically changing (e.g., increase ordecrease) a size or transparency of the position indicator as thedetected (non-zero) hover distance of the input object above thetouch-sensitive surface changes (e.g., increases or decreases, or viceversa)). This is illustrated in FIGS. 7V-7X, for example. In someembodiments, when the input object is well within the hover distancefrom the touch-sensitive surface, the position indicator has a “normal”appearance, e.g., a neutral color or normal opaqueness; and when theinput object is getting very close to the touch-sensitive surface andcontact with the touch-sensitive surface is imminent, the positionindicator takes on a first “warning” appearance, e.g., an orange alertcolor and/or complete opaqueness; and when the input object is gettingvery close to the proximity threshold, and termination of hoverinteraction is imminent, the position indicator takes on a second“warning” appearance, e.g., a red alert color and/or near completetransparency (e.g., as shown in FIG. 7AI).

In some embodiments, the first manner for dynamically varying theappearance of the user interface object is (1618) different from thesecond manner for dynamically varying the appearance. For example,before the input object makes initial contact with the touch-sensitivesurface, the user interface object is in a first state (e.g., a hoverstate), and it visually responds to the changing hover distance in afirst manner (e.g., changing size with varying hover distance); andafter the input object makes the initial contact with thetouch-sensitive surface, the user interface object is in a second state(e.g., a contact state), and it visually responds to the changingintensity of the contact in a second manner (e.g., changing color withvarying contact intensity). In some embodiments, by providingdistinguishable visual feedback regarding whether the object isresponding to a hover portion or a press portion of an input, the deviceprovides a more responsive user interface and allows the user to timelyadjust his/her input to accomplish an intended task (e.g., to continuepushing toward the touch-sensitive surface to make contact with theobject) and/or to avert input mistakes (e.g., to stop pressing harder toavoid meeting an intensity threshold to trigger an unintended action).The more responsive user interface also helps to avoid causing userconfusion during an input because each portion of the input has a directand immediate impact on the visual appearance of the user interface.

In some embodiments, the device visually distinguishes (1620): a hoverstate of the user interface object during which the appearance of theuser interface object is dynamically changed in accordance with thecurrent hover distance, and a contact state of the user interface objectduring which the appearance of the first user interface object isdynamically changed in accordance with the current contact intensity.For example, in some embodiments, a different color or hue is applied tothe user interface object to indicate whether the user interface objectis in the hover state or the contact state (e.g., as shown in FIGS.7V-7AI, color of object 704 changes before and after contact is made).In a more specific example, when a fingertip is hovering over a button,the button has a blue color to indicate that it is in the hover state,and a size that increases with decreasing hover distance; when thefingertip makes contact with the touch-sensitive surface, the buttonturns red and is now in the contact state, and the size of the buttonincreases with increasing contact intensity. In some embodiments, byproviding distinguishable visual feedback regarding whether the objectis in the hover state or the contact state, the device provides a moreresponsive user interface and allows the user to timely adjust his/herinput to accomplish an intended task (e.g., to continue pushing towardthe touch-sensitive surface to make contact with the object) and/or toavert input mistakes (e.g., to stop pressing harder to avoid meeting anintensity threshold to trigger an unintended action). The moreresponsive user interface also helps to avoid causing user confusionduring an input because each portion of the input has a direct andimmediate impact on the visual appearance of the user interface.

In some embodiments, the device aurally distinguishes (1622): a hoverstate of the user interface object during which the appearance of theuser interface object is dynamically changed in accordance with thecurrent hover distance, and a contact state of the user interface objectduring which the appearance of the first user interface object isdynamically changed in accordance with the current contact intensity.For example, in some embodiments, different types of sounds are playedto indicate whether the user interface object is in the hover state orthe contact state. In a more specific example, when a fingertip ishovering over a button, a continuous whirring sound is played toindicate that the button is in the hover state, and the size of the userinterface object increases with decreasing hover distance (e.g., as theuser is pushing down toward the touch-sensitive surface); when thefingertip makes contact with the touch-sensitive surface, a continuousbuzzing sound is played to indicate that the button is now in thecontact state, and the size of the button increases with increasingcontact intensity (e.g., as the user continues to push down against thetouch-sensitive surface). In some embodiments, the frequency or pitch ofthe sound that is played is correlated with (e.g., negatively correlatedwith) the current hover distance during the hover state, and iscorrelated with (e.g., positively correlated with) the current contactintensity during the contact state. Although in the embodimentsdescribed above, the appearance of the user interface object isdynamically varied in accordance with changing hover distances and/orcontact intensities, in some embodiments, only dynamically changedsounds (e.g., sound frequency and/or composition) are used to indicatethe current hover distance and/or the current contact intensity, and thebutton's appearance does not change with the changing hover distanceand/or contact intensity. In some embodiments, when audio feedback isprovided concurrently with the visual feedback, the audio feedbackenhances the visual changes that is occurring in the user interface, andallows the user to know whether the object is responding to a hoverportion or a press portion of an input without focusing on the userinterface visually. In some embodiments, audio feedback is providedwithout accompanying visual feedback, the device ensures that the usercan determine the state of the user interface element based on the audiofeedback, without visually distracting the user. The audio feedbackallows the user to timely adjust his/her input to accomplish an intendedtask (e.g., to continue pushing toward the touch-sensitive surface tomake contact with the object) and/or to avert input mistakes (e.g., tostop pressing harder to avoid meeting an intensity threshold to triggeran unintended action).

In some embodiments, the device provides (1624) a first visual and/oraudio and/or haptic signal in response to detecting the input objectmaking contact with the touch-sensitive surface at the initial contactlocation (e.g., to indicate the transition from the hover state to thecontact state). In some embodiments, by providing an audio and/or visualand/or haptic signal to indicate the transition from the hover stateinto the contact state, the device reduces user confusion when providinginput because the user would not be surprised by a sudden change in userinterface behavior when the user inadvertently makes contact with thetouch-sensitive interface during a hover input.

In some embodiments, the device provides (1626) a second visual and/oraudio and/or haptic signal (e.g., audio signal 722 in FIG. 7AE) inresponse to detecting the input object breaking contact with thetouch-sensitive surface at a final contact location (e.g., to indicatethe transition from the contact state to the hover state). In someembodiments, the second visual and/or audio signal is different from thefirst visual and/or audio signal. In some embodiments, the second visualand/or audio signal is the same as the first visual and/or audio signal.In some embodiments, by providing an audio and/or visual and/or hapticsignal to indicate the transition from the contact state to the hoverstate, the device reduces user confusion when providing input becausethe user would not be surprised by a sudden change in user interfacebehavior when the user inadvertently breaks contact with thetouch-sensitive interface during a press input.

In some embodiments, while dynamically changing the appearance of theuser interface object in accordance with the current contact intensitybetween the input object and the touch-sensitive surface, the devicedetects (1628) the input object breaking contact with thetouch-sensitive surface at a final contact location that corresponds acurrent onscreen location of the user interface object; and in responseto detecting the input object breaking contact with the touch-sensitivesurface, the device dynamically changes the appearance of the userinterface object in a third manner in accordance with the current hoverproximity parameter of the input object (e.g., the appearance of theuser interface object is dynamically varied as the hover distance of theinput object changes), wherein: the first manner by which the appearanceof the user interface object is dynamically changed in accordance withthe current hover proximity parameter before the input object has madethe initial contact with the touch-sensitive surface differs from thethird manner by which the appearance of the user interface object isdynamically changed in accordance with the current hover proximityparameter after the input object has broken the initial contact with thetouch-sensitive surface. This is illustrated in FIG. 7AE-7AI, incontrast to FIGS. 7V-7X. For example, in some embodiments, before thefinger made the initial contact with the button on the touch-screen, thebutton shrinks with decreasing hover distance of the fingertip with afirst variable rate as the fingertip approaches the touch-screen (e.g.,as if the button is being repelled by the approaching fingertip, but iseventually caught up by the approaching fingertip); and immediatelyafter the fingertip is lifted off of the touch screen, the button growswith increasing hover distance of the fingertip at a second variablerate as the fingertip moves away from the touch-screen (e.g., giving theillusion that the button is stuck on the fingertip and is being pulledtoward the user with the fingertip, but eventually breaks away from thepull of the fingertip). In another example, in some embodiments, beforethe finger made the initial contact with the button on the touch screen,the button maintains its size and gets progressively darker withdecreasing hover distance, and after the fingertip makes contact withthe touch-sensitive surface, the button continues to get darker withincreasing contact intensity (and either maintains its size or shrinksin size with increasing contact intensity); then, when the fingertipstarts to ease off the pressure, the button gets progressively largerwith decreasing contact intensity (and either maintains its currentbrightness or gets progressively lighter with decreasing contactintensity); and after the fingertip breaks contact with thetouch-sensitive surface, the button continues to get larger withincreasing hover distance, while the brightness of the button remainsconstant. In other words, before the contact, brightness (and not size)of the user interface object changes with hover distance; and after thecontact, size (and not brightness) of the user interface object changeswith hover distance. In some embodiments, by providing distinguishablevisual feedback regarding whether the object is in the hover state orthe contact state and whether the object is in the hover state before orafter initial contact with the touch-sensitive surface, the deviceprovides a more responsive user interface that helps to reduce userconfusion when providing an input because the user would not besurprised by a sudden change in user interface behavior when the userinadvertently makes contact or breaks contact with the touch-sensitiveinterface during the input.

In some embodiments, across a transition where the input object makescontact with the touch-sensitive surface or where the input objectbreaks contact with the touch-sensitive surface, the device maintains(1630) a direction (e.g., the direction of increasing characteristicvalue or the direction of decreasing value) in which a first visualcharacteristic of the user interface object is dynamically changed inaccordance with the current hover proximity parameter or the currentcontact intensity. This is illustrated in FIGS. 7V-7AB. For example, insome embodiments, if the first visual characteristic has a positivecorrelation with the hover proximity parameter (e.g., increasing sizewith increasing hover distance, decreasing size with decreasing hoverdistance) before the input object makes contact with the touch-sensitivesurface, the first visual characteristic will have a negativecorrelation with the contact intensity (e.g., decreasing size withincreasing contact intensity, and increasing size with decreasingcontact intensity) after the input object makes contact with thetouch-sensitive surface. In a more specific example, the device maydecrease the size of the user interface object with decreasing hoverdistance until the input object reaches the touch-sensitive surface, andthe device will continue to decrease the size of the user interfaceobject with increasing contact intensity while the input object remainsin contact with the touch-sensitive surface. In some embodiments, if thefirst visual characteristic has a negative correlation with the contactintensity before the input object breaks contact with thetouch-sensitive surface, the first visual characteristic has a positivecorrelation with the hover distance after the input object breakscontact with the touch-sensitive surface. In a more specific example,the device may increase the size of the user interface object withdecreasing contact intensity until the user input object breaks contactwith the touch-sensitive surface, and the device will continue toincrease the size of the user interface object with increasing hoverdistance while the input object remains within the threshold hoverdistance above the touch-sensitive surface. By maintaining the directionof change for a first visual characteristic of the object when the userinput transitions from a hover input to a press input, the deviceprovides a smooth transition that is less distracting and feels morenatural to the user when the user pushes down first toward and thenagainst the touch-sensitive surface. This smooth and natural feedbackhelps to reduce user confusion when providing input because the userwould not be surprised by a sudden change in user interface behaviorwhen the user pushes down first toward and then against thetouch-sensitive surface.

In some embodiments, the device detects (1632) a third portion of theinput, wherein detecting the third portion of the input includesdetecting that the current hover proximity parameter ceases to meet thehover criteria while the input object is at a final hover location thatcorresponds to the current onscreen location of the user interfaceobject; and in response to detecting the third portion of the input,restoring the appearance of the user interface object to an initialstate that was shown before the detection of the first portion of theinput. In some embodiments, restoring the appearance of the userinterface object after termination of the hover input conforms to theuser's expectation, helps to avoid user confusion, and reduces users'input mistakes that are made during confusion.

In some embodiments, the device provides (1634) a third visual and/oraudio and/or haptic signal in response to detecting the third portion ofthe input (e.g., to indicate the final exit of the input object from thehover state). This is illustrated in FIG. 7AJ. In some embodiments, thethird visual and/or audio and/or haptic signal is different from thefirst and second visual and/or audio and/or haptic signals. In someembodiments, the third visual and/or audio and/or haptic signal is thesame as the first or second visual and/or audio and/or haptic signals.In some embodiments, by providing an audio and/or visual and/or hapticsignal to indicate the exit from the hover state, the device reducesuser confusion when providing input because the user would not besurprised by a sudden change in user interface behavior when the userinadvertently moves outside of the hover distance during a hover inputafter an initial contact with the touch-sensitive surface.

In some embodiments, before restoration of the appearance of the userinterface object to the initial state is completed, the device displays(1636) an animation showing an overshoot of the restoration and areversal of the overshoot (e.g., showing a bouncy visual effect for therestoration of the user interface object after exiting the hover state).In some embodiments, the magnitude of the overshoot is based on a rateof change of a parameter of the input (e.g., a rate of change of thehover distance of the input, or a rate of change of the intensity of theinput) such that the magnitude of the overshoot increases as the rate ofchange of the parameter increases, and the magnitude of the overshootdecreases as the rate of change of the parameter decreases. By providingthe overshoot animation, the device primes the user of the final stateof the user interface object before the object settles into the finalstate, and thus reduces user confusion and reduces users' input mistakesthat are made during confusion.

In some embodiments, dynamically changing the appearance of the userinterface object includes (1638) dynamically changing one or more ofvisual characteristics selected from a group consisting of: a size, acolor, a hue, a color saturation, a brightness, a boldness, an animationspeed, a vibration frequency, a level of image clarity or detail, anopacity, an image resolution, and a level of deformity.

In some embodiments, while dynamically changing the appearance of theuser interface object in the first manner in accordance with the currenthover proximity parameter of the input object, the device applies (1640)a first dynamically varied sound effect to accompany the dynamicallychanged appearance of the user interface object (e.g., in accordancewith the current hover proximity parameter of the input object or thechanging appearance).

In some embodiments, while dynamically changing the appearance of theuser interface object in the second manner in accordance with thecurrent contact intensity of the contact by the input object, the deviceapplies (1642) a second dynamically varied sound effect to accompany thedynamically changed appearance of the user interface object (e.g., inaccordance with the current hover proximity parameter of the inputobject or the changing appearance).

In some embodiments, while dynamically changing the appearance of theuser interface object in the first manner and in the second manner(e.g., both in accordance with the current hover proximity parameter ofthe input object, and in accordance with the current contact intensityof the contact by the input object), the device applies (1644) a thirddynamically varied sound effect to accompany the dynamically changedappearance of the user interface object, wherein across a transitionwhere the input object makes contact with the touch-sensitive surface orwhere the input object breaks contact with the touch-sensitive surface,the device maintains a direction (e.g., the direction of increasingcharacteristic value or the direction of decreasing value) in which anaudio characteristic (e.g., pitch, number of harmonics) of the thirdsound effect is dynamically changed (e.g., in accordance with thecurrent hover proximity parameter or the current contact intensity, orin accordance with the varying appearance of the user interface object).

In some embodiments, while dynamically changing the appearance of theuser interface object in the first manner or in the second manner(1646): the device detects a current angle (e.g., inclination, tilt,and/or orientation, e.g., as characterized by the inclination andazimuthal angles) of the input object relative to the touch-sensitivesurface; and the device applies a fourth dynamically varied sound effectto accompany the dynamically changed appearance of the user interfaceobject, wherein the fourth dynamically varied sound effect varies inaccordance with the current angle of the input object. For example, insome embodiments, a first whirring sound (e.g., shu-shu-shu) is playedwhen the input object rotates about a vertical axis (e.g., changingazimuthal angle) while maintaining a first fixed inclination angle, anda second whirring sound (e.g., sh-sh-sh) is played when the input objectrotates about the vertical axis (e.g., changing azimuthal angle) whilemaintaining a second fixed inclination angle. In some embodiments, afrequency of each of the whirring sounds increases with increasingrotation speed.

In some embodiments, applying the fourth dynamically varied sound effectto accompany the dynamically changed appearance of the user interfaceobject includes (1648): choosing different sound qualities for thefourth dynamically varied sound effect while dynamically changing theappearance of the user interface object in the first manner and thesecond manner. For example, when the user interface object is in thehover state, the sound quality of the fourth dynamically varied soundeffect indicates friction through air (e.g., input object rotating inair); and while the user interface object is in the contact state, thesound quality of the fourth dynamically varied sound effect indicatefriction on a solid material (e.g., input object scrubbing the userinterface object). In some embodiments, in response to detecting theinput object breaking contact with the touch-sensitive surface at arespective final contact location corresponding to the current onscreenlocation of the user interface object, an ending sound effect to end acurrently applied dynamically varied sound effect is provided. In someembodiments, in response to detecting the input object moving beyond thethreshold hover distance above the touch-sensitive surface at therespective final hover location corresponding to the current onscreenlocation of the user interface object, an ending sound effect to end acurrently applied dynamically varied sound effect is provided.

In some embodiments, while the input object meets the hover criteria(e.g., after the user input object has been selected and picked up bythe input object), the device detects (1650) first lateral movement ofthe input object over the touch-sensitive surface; and in response todetecting the first lateral movement of the input object over thetouch-sensitive surface while the input object meets the hover criteria,the device moves the user interface object across the display inaccordance with the first lateral movement of the input object over thetouch-sensitive surface. In some embodiments, the movement of the userinterface object appears to lag behind the lateral movement of the inputobject.

In some embodiments, while the input object remains in contact with thetouch-sensitive surface (e.g., when the input object meets the longpress criteria, and the user interface object is selected by the inputobject), the device detects (1652) second lateral movement of the inputobject across the touch-sensitive surface; and in response to detectingthe second lateral movement of the input object across thetouch-sensitive surface while the input object remains in contact withthe touch-sensitive surface, the device moves the user interface objectacross the display in accordance with the second lateral movement of theinput object across the touch-sensitive surface. In some embodiments,the user interface object does not lag behind the input object, whenmoving with the input object.

In some embodiments, before selection of the user interface object(e.g., before selection of the user interface object in response to aninitial selection input (e.g., a tap or long press on the user interfaceobject)), while the input object meets the hover criteria, the devicedetects (1654) third lateral movement of the input object across thetouch-sensitive surface; and in response to detecting the third lateralmovement of the input object across the touch-sensitive surface whilethe input object meets hover criteria, the device distorts the userinterface object in accordance with the third lateral movement of theinput object across the touch-sensitive surface, without moving the userinterface object.

It should be understood that the particular order in which theoperations in FIGS. 16A-16E have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 1500, 1700, 1800, 1900, 2000, 2100, 2200, 2300 and 2400) arealso applicable in an analogous manner to method 1600 described abovewith respect to FIGS. 16A-16E. For example, the contacts, gestures,input objects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described above with reference to method 1600 optionally haveone or more of the characteristics of the contacts, gestures, inputobjects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described herein with reference to other methods describedherein (e.g., methods 1500, 1700, 1800, 1900, 2000, 2100, 2200, 2300 and2400). For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 16A-16E are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, detection operations 1604 and 1608 and changing operations 1606and 1610 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

FIGS. 17A-17C are flow diagrams illustrating a method 1700 ofinteracting with selectable text through proximity-based inputs andcontact-based inputs in accordance with some embodiments. The method1700 is performed at an electronic device (e.g., device 300, FIG. 3, orportable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the electronic deviceincludes one or more first sensors to detect proximity of an inputobject above the touch-sensitive surface (e.g., proximity sensors (suchas infrared sensors), capacitive sensors in the touch sensitive surface,or cameras next to the touch-sensitive surface). In some embodiments,the electronic device includes one or more second sensors to detectintensity of contact of the input object with the touch-sensitivesurface. In some embodiments, the one or more second sensors aredifferent from the one or more first sensors. In some embodiments, theone or more second sensors are the same as the one or more firstsensors. In some embodiments, the touch-sensitive surface and thedisplay are integrated into a touch-sensitive display. In someembodiments, the display is a touch-screen display and thetouch-sensitive surface is on or integrated with the display. In someembodiments, the display is separate from the touch-sensitive surface.Some operations in method 1700 are, optionally, combined and/or theorder of some operations is, optionally, changed.

As described below, the method 1700 provides an intuitive way tointeract with selectable text. In particular, this method provides anintuitive and efficient way of switching from a cursor placement mode toa text selection mode, without requiring extra actions on the part ofthe user (e.g., a press input with increased contact intensity above athreshold intensity, or selection of an affordance), thus making theuser interaction with the user interface faster and more streamlined.The method reduces the number, extent, and/or nature of the inputs froma user when interacting with selectable text, thereby creating a moreefficient human-machine interface. For battery-operated electronicdevices, enabling a user to select text faster and more efficientlyconserves power and increases the time between battery charges.

The device displays (1702) a position indicator (e.g., a cursor, aspotlight, or text highlighting) (e.g., cursor 738) within text (e.g.,editable text or non-editable text) on the display while an input object(e.g., a finger or a stylus) above the touch-sensitive surface meetshover criteria. For example, while the user interface object isdisplayed, the device detects that a finger (e.g., finger 734)approaches the user interface object (e.g., selectable text 732) fromabove touch-sensitive surface (e.g., touch-screen 112) without makingcontact with the touch-sensitive surface, while remaining within athreshold distance above the touch-sensitive surface, as shown in FIGS.7AK-7AL.

While the position indicator (e.g., cursor 738) is displayed within thetext (e.g., text 732) on the display, the device detects (1704) a firstmovement of the input object that includes a component of movementparallel to the touch-sensitive surface, wherein the input objectcontinues to meet the hover criteria during the first movement. Forexample, while the position indicator is displayed, the device detectsthat a finger moves laterally across the space above the touch-sensitivesurface without making contact with the touch-sensitive surface, whileremaining within a threshold distance above the touch-sensitive surface.This is shown in FIGS. 7AL-7AM (e.g., movement of finger 734 abovetouch-screen 112 causes movement of cursor 738 in text 732).

In response to detecting the first movement of the input object over thetouch-sensitive surface, the device moves (1706) the position indicator(e.g., cursor 738) within the displayed text in accordance with thefirst movement of the input object. For example, as a hovering fingermoves across the touch-sensitive surface, a cursor on the display tracksthe movement of the hovering finger and moves among allowed cursorpositions in the text. This is illustrated in FIGS. 7AL-7AM.

After moving the position indicator within the displayed text inaccordance with the first movement of the input object, the devicedetects (1708) a second movement of the input object that includes acomponent of movement parallel to the touch-sensitive surface. Forexample, after hovering across the touch-sensitive surface to positionthe cursor at a desired location within the text, a finger makes contactwith the touch-sensitive surface at a first location and then movesacross the touch-sensitive surface while maintaining contact with thetouch-sensitive surface to select text.

In response to detecting the second movement of the input object acrossthe touch-sensitive surface: in accordance with a determination that thesecond movement of the input object is detected while the input objectis in contact with the touch-sensitive surface, the device selects(1710) text in accordance with the second movement of the input objectacross the touch-sensitive surface while the input object remains incontact with the touch-sensitive surface (e.g., a current end boundaryof the text selection on the display is determined based on the currentposition of the input object on the touch-sensitive surface during thesecond movement). This is shown in FIGS. 7AN-7AO (e.g., movement offinger 734 across touch-screen 112 cause selection of text).

In some embodiments, the device detects (1712) the input object makingcontact with the touch-sensitive surface at a first location on thetouch-sensitive surface followed by the second movement of the inputobject across the touch-sensitive surface; and in response to detectingthe input object making contact with the touch-sensitive surface at thefirst location on the touch-sensitive surface followed by the secondmovement of the input object across the touch-sensitive surface: thedevice starts text selection within the text at the first location onthe display that corresponds to the first location on thetouch-sensitive surface (e.g., the contact position determines astarting boundary of the text selection), and the device expands theselected text in accordance with the second movement of the input objectacross the touch-sensitive surface. This is illustrated in FIGS.7AN-7AO, for example.

In some embodiments, in response to detecting the second movement of theinput object across the touch-sensitive surface: in accordance with adetermination that the second movement of the input object is detectedwhile the input object is hovering over the touch-sensitive surfacewithout making contact with the touch-sensitive surface, the devicemoves (1714) the position indicator in accordance with the second inputwithout selecting text. This is shown in FIGS. 7AP-7AQ, for example.

In some embodiments, the hover criteria include (1716) a criterion thatis met when a hover proximity parameter of the input object is less thana threshold proximity value. For example, the detected distance of afingertip above the touch-sensitive surface is less than a thresholddistance. As used in the specification and claims, the term “hoverproximity parameter” refers to the (non-zero) distance of the inputobject above the touch-sensitive surface or to a substitute (proxy) forthe distance of the input object above the touch-sensitive surface. Insome embodiments, a change in capacitance detected on thetouch-sensitive surface due to changing distance of an input objectabove the touch-sensitive surface is a proxy for the distance of theinput object above the touch-sensitive surface. In some embodiments, thehover criteria further include a criterion that the input object is nottouching the touch-sensitive surface.

In some embodiments, the position indicator is (1718) initiallydisplayed within the text in response to detecting that the hoverproximity parameter of the input object is less than the thresholdproximity value above an initial location on the touch-sensitive surface(e.g., when the finger moves towards a touch-screen display and comeswithin a threshold hover distance above the touch-screen display, thehover criteria are met by the finger and a hover input is detected).This is shown in FIGS. 7AK-7AL, for example. In some embodiments, whenthe finger comes close to a touch-screen display without touching it, acursor or other position indicator is displayed; and when the fingermoves away from the touch-screen display, the cursor ceases to bedisplayed. In some embodiments, the position indicator is displayed onlywhen the input object is detected above a region in which selectabletext is displayed, and ceases to be displayed when the finger movesoutside of the region in which the selectable text is displayed even ifthe hover proximity parameter of the input object remains below thethreshold proximity value.

In some embodiments, displaying the position indicator within the textincludes (1720) displaying the position indicator (e.g., cursor 738)within the text (e.g., text 732) at a location that is based on one ormore of: a position of a projection of a tip (or other representativeportion) of the input object on the touch-sensitive surface (e.g., (x,y)position 504 in FIG. 7AL); an orientation of the input object relativeto the touch-sensitive surface; a tilt of the input object relative tothe touch-sensitive surface; and a distance of the input object relativeto the touch-sensitive surface (e.g., distance 514, FIG. 7AL). In someembodiments, a cursor, spotlight, or text highlighting is positioned inthe text as if it is projected from the tip of a finger onto thetouch-screen display along the body of the finger. And the location ofthe position indicator changes dynamically as the position, orientation,tilt, and/or distance of the hovering finger changes while the hoverproximity parameter of the hovering finger continues to meet the hovercriteria. By displaying the position indicator at a location that isbased on one or more factors other than the position of the tip of theinput object, the device reduces the negative impact of the tipobscuring the position indicator, and thereby reduces user mistakes andimproves operability of the device.

In some embodiments, while the hover criteria are met, the devicedisplays (1722) a magnifier object (e.g., a magnifying window or aloupe) (e.g., magnifying loupe 736) over a portion of the displayedtext, wherein the magnifier object displays a magnified image of theposition indicator and text adjacent to the position indicator (withoutmagnifying other portions of the displayed text). In some embodiments,the magnifier object continues to be displayed while the input object isin contact with the touch-sensitive surface. This is illustrated in FIG.7AN, for example.

In some embodiments, in response to detecting the first movement of theinput object over the touch-sensitive surface (1724): the device movesthe magnifier object in accordance with the first movement of the inputobject over the touch-sensitive surface; and the device updates themagnifier object to display an updated magnified image of the positionindicator and text adjacent to the position indicator. This is shown inFIG. 7AL-7AM, for example. By updating the magnifier object to displayan updated magnified image of the position indicator and the textadjacent to the position indicator, the device provides a clearer andunobscured view of the text that is in proximity to the input object,and allows the user to provide proper input (e.g., text selection orcursor placement) when interacting with the user interface.

In some embodiments, while a first portion of the text is selected onthe display in accordance with the second movement of the input object,the device detects (1726) liftoff of the input object from thetouch-sensitive surface; and, in response to detecting the liftoff ofthe input object, maintaining selection of the first portion of the texton the display. This is shown in FIG. 7AP, for example. In someembodiments, liftoff of the input object is detected when the inputobject breaks contact with the touch-sensitive surface. In someembodiments, liftoff of the input object is detected when the inputobject breaks contact with the touch-sensitive surface and moves beyonda threshold proximity distance above the touch-sensitive surface.Alternatively, in some embodiments, liftoff of the input object causesthe selection to be canceled, unless a press input is detected within apredefined time prior to detecting the liftoff. In some embodiments,maintaining selection of the selected text upon lift-off withoutrequiring additional confirmation input from the user simplifies theuser interaction with the device, thereby making the device-userinterface more efficient. In some embodiments, the device maintainsselection of the selected text upon a confirmation input (e.g., a pressinput) before lift-off of the contact by the input object. Requiring aconfirmation input to maintain selection of the selected text reducesuser mistakes and avoid inefficiencies that are caused due to usermistakes.

In some embodiments, in response to detecting the liftoff of the inputobject, the device displays (1728) a menu of options for the selectedfirst portion of the text (e.g., a menu with options to copy, paste,delete, look-up, etc.). In some embodiments, the menu is displayedadjacent to the selected text. In some embodiments, the menu isdisplayed when the device determines that the input object is beyond athreshold proximity distance above the touch-sensitive surface. This isillustrated in FIG. 7AU, for example. In some embodiments, the menu isdisplayed when the device determines that the input object is no longerin contact with the touch-sensitive surface, irrespective of whether theinput object is still within the threshold proximity distance above thetouch-sensitive surface. By automatically displaying a menu bar afterlift-off of the input object and while selection of text is maintained,the user can immediately specify an operation to be performed withrespect to the selected text, without having to provide additional inputto invoke the menu bar. Thus, automatic displaying the menu bar at thisappropriate occasion helps to simplify the user's interaction with thedevice and improves the efficiency of the device-user interface.

In some embodiments, after detecting the liftoff of the input object(1730): the device determines whether the input object meets the hovercriteria (e.g., determining whether the input object is beyond athreshold proximity distance above the touch-sensitive surface); inaccordance with a determination that the input object meets the hovercriteria, the device maintains display of the position indicator on thedisplay; and in accordance with a determination that the input objectceases to meet the hover criteria (e.g., upon determining that the inputobject is beyond the threshold proximity distance above thetouch-sensitive surface), the device ceases to display the positionindicator on the display. This is illustrated in FIGS. 7AT-7AU, forexample. In some embodiments, if the magnifier object (e.g., themagnification window, the loupe, etc.) is displayed during the hoverinput, when the input object is lifted beyond the threshold proximitydistance above the touch-sensitive surface, the device also ceases todisplay the magnifier object. This is illustrated in FIG. 7AU, forexample. In some embodiments, maintaining the display of the positionindicator after lift-off of the input object but while the input objectis still hovering above the touch-sensitive surface, the device allowsthe user to continue with the current input (e.g., to reposition theposition indicator) without starting a new input. This improves theefficiency of the device-user interface because the user is not requiredto restart the process to position the position indicator by exiting thehover range, and reenter the hover range with the input object.

In some embodiments, after detecting the liftoff of the input object(e.g., when the input object breaks contact with the touch-sensitivesurface but remains within a threshold proximity distance above thetouch-sensitive surface) (1732): the device detects a third movementover the touch-sensitive surface of the input object while the inputobject meets the hover criteria; and, in response to detecting the thirdmovement of the input object over the touch-sensitive surface, thedevice moves the position indicator in accordance with the thirdmovement of the input object, while maintaining the selection of thefirst portion of the text on the display. This is illustrated in FIG.7AQ, for example. By maintaining the selection of the selected textwhile allowing movement of the position indicator to a new location, thedevice offers the user the option to start a new selection and theoption to keep the current selection until the user makes a decisionregarding the two options (e.g., by exiting the hover range, or bytouch-down on the touch-sensitive surface again). By allowing the userlonger time to consider his/her options, the device helps to reduce usermistakes and improves efficiency of the device-user interface byreducing user mistakes.

In some embodiments, after moving the position indicator in accordancewith the third movement of the input object over the touch-sensitivesurface, the device detects (1734) the input object making contact withthe touch-sensitive surface at a second location on the touch-sensitivesurface; and, in response to detecting the input object making contactwith the touch-sensitive surface at the second location on thetouch-sensitive surface: the device cancels selection of the firstportion of the text; and the device restarts text selection at alocation on the display that corresponds to the second location on thetouch-sensitive surface (and expanding the text selection in accordancewith subsequent movement of the input object).

It should be understood that the particular order in which theoperations in FIGS. 17A-17C have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 1500, 1600, 1800, 1900, 2000, 2100, 2200, 2300 and 2400) arealso applicable in an analogous manner to method 1700 described abovewith respect to FIGS. 17A-17C. For example, the contacts, gestures,input objects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described above with reference to method 1700 optionally haveone or more of the characteristics of the contacts, gestures, inputobjects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described herein with reference to other methods describedherein (e.g., methods 1500, 1600, 1800, 1900, 2000, 2100, 2200, 2300 and2400). For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 17A-17C are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, detection operations 1704 and 1708, moving operation 1704, andselection operation 1710 are, optionally, implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

FIGS. 18A-18G are flow diagrams illustrating a method 1800 ofinteracting with a user interface object through proximity-based andcontact-based inputs in accordance with some embodiments. The method1800 is performed at an electronic device (e.g., device 300, FIG. 3, orportable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the electronic deviceincludes one or more first sensors to detect proximity of an inputobject (e.g., a finger or a stylus) above the touch-sensitive surface(e.g., proximity sensors (such as infrared sensors), capacitive sensorsin the touch sensitive surface, or cameras next to the touch-sensitivesurface) and one or more second sensors to detect intensities of contactof the input object with the touch-sensitive surface. In someembodiments, the one or more second sensors are different from the oneor more first sensors. In some embodiments, the one or more secondsensors are the same as the one or more first sensors. In someembodiments, the touch-sensitive surface and the display are integratedinto a touch-sensitive display. In some embodiments, the display is atouch-screen display and the touch-sensitive surface is on or integratedwith the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 1800 are, optionally,combined and/or the order of some operations is, optionally, changed.

As described herein, method 1800 relates to a heuristic for determiningwhether to confirm or cancel a user interface operation after a previewof the user interface operation has been provided in response to ahover-move input by an input object. Specifically, after the devicedetects an input that corresponds to the start of the user interfaceoperation, the device detects a hover-move input that conveys specificparameters of the user interface operation with at least a lateralmovement of the input object while the input object hovers above thetouch-sensitive surface. The device provides a preview of the userinterface operation in accordance with the hover-move input. After thepreview has been provided, depending on whether the input object makescontact with the touch sensitive surface or moves away from thetouch-sensitive surface to end the hover-move input, the device eitherconfirms the user interface operation or cancels the user interfaceoperation. Method 1800 makes use of the two natural and intuitive waysto conclusion a hover-move input, namely (1) making contact with thetouch-sensitive surface and (2) moving away from touch-sensitivesurface, to either confirm or cancel a user interface operation afterthe device has provided a preview of the user interface operation inaccordance with the hover-move input. As a result, the device is able toprovide improved feedback to the user regarding the full effect of anoperation without requiring the user's commitment to actually performthe operation. The confirmation and cancellation of the operation takesplace in response to a natural conclusion of the hover-move input,without requiring any additional steps taken by the user. Providing suchimproved feedback and reducing the number of steps to confirm or cancelan operation in accordance with the method described herein enhance theoperability of the device and make the user-device interface moreefficient (e.g., by helping the user to achieve an intended result byproviding the required inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reduce powerusage and improve battery life of the device (e.g., by enabling the userto use the device more quickly and efficiently). Additionally, providingthe preview of the operation in response to a hover-move input furtherenhances the operability of the device (e.g., by allowing the user tohave a better view of the user interface during the input and therebyreducing user mistakes when operating the device) and improves thelongevity of the device (e.g., by eliminating unnecessary pressure andfriction on the touch-sensitive surface during the input, and therebyreducing structural fatigue of the touch-sensitive surface).

The device displays (1802) a user interface on the display (e.g.,including displaying a first user interface object (e.g., an indicatoron a slider control, a dial, an app icon on a home screen, a list itemin a list, a resize handle on an object, or an edge of a selection box,etc.) at a first location on the display). The device detects (1804) afirst input by the input object that corresponds to a start of a firstuser interface operation (e.g., including detecting selection of thefirst user interface object by the input object as the start of a moveoperation (e.g., to change a current value of the slider control ordial, to reconfigure the home screen, to reorder a list, or to resize anobject or a selection box) (e.g., selection is triggered by tapping onthe first user interface object, pressing on the first user interfaceobject, touching the first user interface object and holding for aperiod of time, or hovering over the first user interface object at arequired distance above the display and/or hold for a threshold amountof time, etc., by the input object). In some embodiments, selection ofthe first user interface object is indicated by visual, audio, and/orhaptic feedback. After detecting the first input that corresponds to thestart of the first user interface operation (e.g., start of a moveoperation, start of a resize operation, etc.) and while the input objectmeets hover proximity criteria (e.g., the input object is within a hoverproximity range above the touch-sensitive surface and is not in contactwith the touch-sensitive surface), the device detects (1806) lateralmovement of the input object (e.g., lateral movement of the input objectincludes a component of the movement of the input object that isparallel to the touch-sensitive surface). In response to detecting thelateral movement of the input object while the input object meets thehover proximity criteria, the device updates the user interface toindicate a preview of the first user interface operation. For example,when the first user interface operation is a move operation, the previewof the first user interface operation includes moving the first userinterface object from the first location to a second location on thedisplay, wherein the second location is distinct from the firstlocation. This is illustrated in FIGS. 8A-8F, the preview shows thaticon 806 is moved by a hover-move input. In another example, when thefirst user interface operation is a resize operation, the preview of thefirst user interface operation includes moving the resize handle or edgeof an object from the first location to a second location that isdistinct from the first location on the display). This is illustrated inFIGS. 8P-8R, where the preview shows selection object 834 is resizedwith a hover-move input by finger 734. In some embodiments, the previewof the first user interface operation further includes a visualindication of other changes that would occur as a result of the move orresize operation, such as rearrangement of the other user interfaceobjects in the user interface to make room for the user interface objectthat is being moved or resized. This is illustrated in FIGS. 8C-8F,where other icons (e.g., icons 808, 810, 812, and 814) are rearranged aspart of the preview of the move operation, for example. While the userinterface is updated to indicate the preview of the first user interfaceoperation (e.g., while the first user interface object (e.g., theselected icon, list item, resize handle, or edge) is at the secondlocation on the display), the device detects (1810) that the inputobject no longer meets the hover proximity criteria (e.g., the inputobject is lifted away from the touch-sensitive surface or the inputobject has made contact with the touch-sensitive surface). In responseto detecting that the input object no longer meets the hover proximitycriteria: in accordance with a determination that the input object nolonger meets the hover proximity criteria because the input object hasexited a hover proximity range of the touch-sensitive surface, thedevice cancels (1812) the first user interface operation (e.g.,including reversing the update that has been made to the user interfaceby restoring the first user interface object from the second location tothe first location on the display); and in accordance with adetermination that the input object no longer meets the hover proximitycriteria because the input object has made contact with thetouch-sensitive surface, the device confirms the first user interfaceoperation (e.g., including completing the operation by releasing thefirst user interface object to the second location on the display orautomatically releasing the first user interface object to a thirdlocation that is distinct from the first location and the secondlocation on the display (e.g., a nearest snap location corresponding tothe second location, including maintaining the selection at the updatedsize after lift-off of the contact)). This is illustrated in FIGS.8A-8J, where icon 806 is moved by a hover-move input. Move of icon 806is confirmed when finger 734 makes contact (e.g., contact 818) with thetouch-screen before lift-off, and move of icon 806 is canceled whenfinger 734 does not make contact with the touch-screen before beinglifted out of the hover proximity range above the touch-screen. This isalso illustrated in FIGS. 8P-8V, where selection object 834 is resizedwith a hover-move input by finger 734. The resizing of selection object834 is confirmed when finger 734 makes contact (e.g., contact 848) withthe touch-screen before lift-off, and the resizing of selection object843 is canceled with finger 734 does not make contact with thetouch-screen before being lifted out of the hover proximity range abovethe touch-screen.

In some embodiments, the user interface includes (1814) a first item ata first location (e.g., a control (e.g., an indicator on a slidercontrol or dial) on a user interface, an object (e.g., a shape) on acanvas, an item (e.g., a song or weather item) in a list of items (e.g.,a playlist or a list of weather items for different cities), an icon inan arrange of icons (e.g., an application icon in a grid of applicationicons on a home screen, as shown in FIGS. 8A-8J), a resize handle or amoveable edge of a resizable object (e.g., a resizable object, aselection box, or a text selection within selectable text, as shown inFIGS. 8P-8V), or other content or control in the user interface (e.g.,content of a document displayed in a window or in a display region ofthe display). The first user interface operation includes an operationto relocate the first item on the display (e.g., the operation is a moveoperation or a scroll operation, and the start of the operation isselection of an item that is to be moved or triggering of a userinterface scrolling mode). Updating the user interface to indicate apreview of the first user interface operation includes moving the firstitem from a first location to a second location on the display inaccordance with the lateral movement of the input object (e.g., thelocation of the first item change when the first item is moved relativeto the user interface or relative to another object on the userinterface (e.g., a reference position on a slider or scroll bar), orwhen the user interface is shifted or scrolled as a whole, in accordancewith the lateral movement of the input object). Providing the preview ofthe move operation in response to a hover-move input enhances theoperability of the device (e.g., by allowing the user to have a betterview of the user interface during the input and thereby reducing usermistakes when operating the device) and improves the longevity of thedevice (e.g., by eliminating unnecessary pressure and friction on thetouch-sensitive surface during the input, and thereby reducingstructural fatigue of the touch-sensitive surface).

In some embodiments, cancelling the first user interface operation inaccordance with a determination that the input object no longer meetsthe hover proximity criteria because the input object has exited a hoverproximity range of the touch-sensitive surface includes (1816) restoringthe first item to an original location of the first item on the displayafter detecting that the input object no longer meets the hoverproximity criteria (e.g., the items' original location is an location ofthe first item before the first input by the input object thatcorresponds to the start of the first user interface operation and thelateral movement of the input object were detected). This is illustratedin FIGS. 8I-8J, and FIGS. 8R, 8U-8V, for example. In some embodiments,the item's original location is the same as the first location, and insome embodiments, the item's original location is slightly offset fromthe first location (e.g., when the first item jumps out of its originallocation upon selection of the first item). In some embodiments,restoring the first item to its original location on the displayincludes moving the first item back to its original location on the userinterface before the move. In some embodiments, restoring the first itemto its original location on the display includes restoring the userinterface to its original state before the user interface is scrolled orshifted in accordance with the movement of the input object. In someembodiments, the device displays an animation showing the first itemflying back to its original location and settles into its originallocation. In some embodiments, the device generates a tactile output toindicate that the move has been canceled and the first item has settledback into its original location. Providing a preview of a move operationin accordance with a hover-move input and determining whether to cancelthe move operation depending on how the hover-move input ends (e.g., bytouching down on the touch-sensitive surface or moving away from thetouch-sensitive surface) enhance the operability of the device and makethe user-device interface more efficient (e.g., by reducing the numberof steps needed to cancel the move operation).

In some embodiments, confirming the first user interface operation inaccordance with a determination that the input object no longer meetsthe hover proximity criteria because the input object has made contactwith the touch-sensitive surface includes (1818) displaying the firstitem at a final location that is distinct from the first location afterdetecting that the input object no longer meets the hover proximitycriteria (e.g., the final-location is a drop-off location of the firstitem and the item remains at the drop-off location after lift-off of theinput object from the touch-sensitive surface is detected). This isillustrated in FIGS. 8F-8H and 8R-8T, for example. In some embodiments,the item's final location is the same as the second location, and insome embodiments, the item's final location is slightly offset from thesecond location (e.g., when the first item settles into its finallocation after drop-off of the first item upon the input object makingcontact with the touch-sensitive surface, or lift-off of the contact).In some embodiments, the item's final location is a nearest snaplocation (e.g., a third location that is distinct from the firstlocation and the second location) for the first item from the locationof the initial contact with the touch-sensitive surface by the inputobject. In some embodiments, the item's final location on the display isthe location of the first item on the user interface when the userinterface has settled at its final location after having been scrolledor shifted in accordance with the movement of the input object. In someembodiments, a tactile output is generated to indicate that the firstitem has settled into its final location in the user interface.Providing a preview of a move or scroll operation in accordance with ahover-move input and determining whether to confirm the move or scrolloperation depending on how the hover-move input ends (e.g., by touchingdown on the touch-sensitive surface or moving away from thetouch-sensitive surface) enhance the operability of the device and makethe user-device interface more efficient (e.g., by reducing the numberof steps needed to confirm the move or scroll operation).

In some embodiments, the device detects (1820) a second input by theinput object (e.g., either before the first input is detected or afterthe first input has been completed), wherein the second inputcorresponds an operation to display content associated with the firstitem, and wherein the second input does not correspond to the start ofthe first user interface operation (e.g., the second input is a tap onthe first item, and not a touch-hold or a press input to select thefirst item for subsequent movement in accordance with a hover movementof the input object). In response to detecting the second input thatcorresponds to an operation to display content associated with the firstitem, the device displays first content associated with the first item.For example, when a tap input is detected on the application icon, thedevice launches an application corresponding to the application icon,and a user interface of the application is displayed. When a tap inputis detected on a list item (e.g., a representation of an electronicmessage in a list of electronic messages, a representation of electronicmessage conversation in a list of electronic messages, a representationof a contact in a list of contacts), the device displays additionalcontent corresponding to the list item (e.g., an electronic message, anelectronic message conversation, or a contact card). In contrast to thefirst input (e.g., a light press input or a touch-and-hold input) thatcorresponds to an operation to move the first item, the second inputdoes not include a contact with an intensity that exceeds an intensitythreshold or does not include a contact that is maintained for more thana threshold amount of time. Using different inputs for displayingcontent and performing the first user interface operation (e.g., a moveoperation) in association with the first user interface enhance theoperability of the device and make the user-device interface moreefficient (e.g., by providing additional functionality and controlfunctions without cluttering the UI with additional displayed controls)which, additionally, reduce power usage and improve battery life of thedevice (e.g., by enabling the user to use the device more quickly andefficiently).

In some embodiments, while moving the first item from the first locationto the second location on the display in accordance with the lateralmovement of the input object (e.g., when moving the first item relativeto the user interface or scrolling the user interface as a whole inaccordance with the lateral movement of the input object), the devicedynamically adjusts (1822) an appearance of the first item in accordancewith a current hover proximity parameter of the input object (e.g.,dynamically adjusting a size, hue, opacity, and/or other visual propertyof the first item in accordance with a current hover distance of theinput object above the touch-sensitive surface while the first item isbeing dragged across the display in accordance with the lateral hovermovement of the input object). This is illustrated in 8D-8E where thesize of icon 806 is varied dynamically with hover distance 514 of finger734, for example. In some embodiments, the movement of the first itemlags behind the lateral hover movement of the input object when theinput object accelerates in accordance with simulated inertia of thefirst item. In some embodiments, the first item and the input objectmove with different speeds, and the lag between the first item and theinput object is a function of the velocity of the input object. Thebehavior of the first item is different when it is being moved by theinput object while the input object hovers above the touch-sensitivesurface and when it is being moved by the input object while the inputobject maintains contact with the touch-sensitive surface. For example,in a normal drag scenario, the input object maintains contact with thetouch-sensitive surface during the lateral movement, and the first itemhas the same speed as the contact when it is dragged by the input objectacross the display. Even if an item lags behind an input object during anormal drag by contact, the appearance of the item does not vary duringits movement (e.g., does not vary in accordance with the hover proximityparameter of the input object). Dynamically adjusting the visualfeedback (e.g., adjusting the appearance of the first item) inaccordance with a current hover proximity parameter of the input objectduring the move or scroll operation enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to achieve an intended result by providing the requiredinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device (e.g., by enabling the user to use the device morequickly and efficiently).

In some embodiments, the device detects (1824) a third input by theinput object that corresponds to a start of a second operation torelocate the first item on the display (e.g., after the first userinterface operation has either been confirmed or canceled). In someembodiments, the first input and the third input are of the same type,e.g., a touch and hold input, or a light press input. In someembodiments, the first input and the third input are of distinct types,e.g., the first input is a touch-and-hold input, and the third input isa press input, or vice versa. After detecting the third input thatcorresponds to the start of the second operation to relocate the firstitem on the display, the device detects second lateral movement of theinput object while the input object maintains contact with thetouch-sensitive surface (e.g., the input object drags across thetouch-sensitive surface after the first item has been selected by thesecond input for the second operation to relocate the first item). Inresponse to detecting the second lateral movement of the input objectwhile the input object maintains contact with the touch-sensitivesurface, the device moves the first item from a third location (e.g., anoriginal location of the first item, or a location slightly offset fromthe original location of the first item)(e.g., the third location is thesame as the first location) to a fourth location (e.g., a location thatis distinct from the third location)(e.g., the fourth location is thesame as the second location) on the display in accordance with thesecond lateral movement of the input object (e.g., the contact drags thefirst item across the touch-sensitive surface). Upon moving the firstitem from the third location to the fourth location, the device detectsthat the input object is no longer in contact with the touch-sensitivesurface (e.g., the input object is lifted away from the touch-sensitivesurface, and optionally out of the hover proximity range above thetouch-sensitive surface). In response to detecting that the input objectis no longer in contact with the touch-sensitive surface: in accordancewith a determination that the fourth location corresponds to a permitteddrop-off location for the first item on the display, the device displaysthe first item at a final location on the display that corresponds tothe fourth location (e.g., the final location is the fourth location ora snap location nearest the fourth location); and in accordance with adetermination that the fourth location corresponds to a forbiddendrop-off location for the first item on the display, the device restoresthe first item to an original location of the first item on the displaythat corresponds to the third location. For example, in a normal drag bycontact, the item is dropped off at the final location of the draggesture as long as the final location is an acceptable drop-offlocation. Upon lift-off, the item remains at that location; theoperation to relocate the first item is completed upon lift-off. This isillustrated in FIGS. 8K-8O, where icon 806 is dragged by a contact anddropped off at a new location, for example. If the user were to cancelthe relocation of the first item, the user has to drag the first itemmanually back to its original location. Allowing a move or scrolloperation to be carried out by both a move input during hover and a moveinput while maintaining contact provides more flexibility to the user incarrying out a desired task. In addition, this flexibility allows a userto select the more appropriate gesture to carry out a move operation(e.g., it is more efficient to drag while maintaining contact if theuser is certain of the move operation, and it is more efficient to dragwhile hovering if the user is likely to cancel the move operation afterseeing a preview of the movement operation). Thus, providing multiplealternative ways to carry out a move or scroll operation as describedherein enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended result by providing the required inputs, reducing the number ofsteps needed to perform a desired task, and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device (e.g., by enablingthe user to use the device more quickly and efficiently).

In some embodiments, the user interface includes (1826) an arrangementof items (e.g., a list of items or a grid of application launch icons)that includes at least the first item and a second item in a firstconfiguration (e.g., in a first sequential order or a first layout). Theoperation to relocate the first item on the display includes anoperation to rearrange the arrangement of items (e.g., reordering thelist of items or rearranging the grid of application icons). The startof the first user interface operation includes selection of the firstitem. Detecting the input by the input object that corresponds to astart of the first user interface operation includes detecting a contactby the input object with the touch-sensitive surface at a location thatcorresponds to the first item in the arrangement of items, and detectingthat the contact is maintained at the location for more than a firstthreshold amount of time (e.g., detecting a tap-hold input directed tothe first item to select the first item). Alternatively, detecting theinput by the input object that corresponds to a start of the first userinterface operation includes detecting a contact by the input objectwith the touch-sensitive surface at a location that corresponds to thefirst item in the arrangement of items, and detecting that acharacteristic intensity of the contact increases above a firstthreshold intensity (e.g., detecting a light press input directed to thefirst item to select the first item). In response to detecting the inputby the input object that corresponds to the start of the first userinterface operation (e.g., in response to detecting the input to selectthe first item), the device visually indicates selection of the firstitem (e.g., showing that the first item moves away from its originalz-position toward the input object (e.g., the first item “jumps out of”its original location or slot in the user interface towards the inputobject)). Detecting lateral movement of the input object includesdetecting lateral movement of the input object by more than a firstthreshold distance. In some embodiments, the first threshold distance isa threshold distance for determining whether the input object is keptsubstantially stationary or has moved. In some embodiments, the firstthreshold distance is a threshold distance for determining whether thefirst item is to be pulled away from its original location (e.g., pulledout of its original slot or snap location) or remains at its originallocation) after the first item is selected. Updating the user interfaceto indicate a preview of the first user interface operation furtherincludes moving at least the second item (and other items in the list orgrid) in the user interface in accordance with movement of the firstitem from the first location to the second location. For example, insome embodiments, when the first item is near the location of the seconditem in the user interface, the second item moves away from its originallocation in the user interface to provide an acceptable drop-offlocation for the first item in the user interface. In some embodiments,after the first item has moved out of its original location in the userinterface, the second item moves away from its own original location inthe user interface into the original location of the first item to fillthe location that has been vacated by the first item). Providing thepreview of an rearrangement or reordering operation in response to ahover-move input enhances the operability of the device (e.g., byallowing the user to have a better view of the user interface during theinput and thereby reducing user mistakes when operating the device) andimproves the longevity of the device (e.g., by eliminating unnecessarypressure and friction on the touch-sensitive surface during the input,and thereby reducing structural fatigue of the touch-sensitive surface).

In some embodiments, cancelling the first user interface operation inaccordance with a determination that the input object no longer meetsthe hover proximity criteria because the input object has exited a hoverproximity range of the touch-sensitive surface further includes (1828):restoring the first item and the second item (and any other items in thelist or grid) to respective original locations of the first item and thesecond item (and any other items in the list or grid) in the userinterface (which has been kept stationary on the display) afterdetecting that the input object no longer meets the hover proximitycriteria. (e.g., the list of items is displayed in the first order afterthe input object has exited the hover proximity range of thetouch-sensitive surface; the grid of application items is displayed inthe first configuration after the input object has exited the hoverproximity range of the touch-sensitive surface (e.g., as shown in FIG.8J)). In some embodiments, tactile outputs are generated by the deviceto indicate that the first item and the second item (and other items)are restored to their original locations after the input object islifted out of the hover proximity range above the touch-sensitivesurface (e.g., the rearrangement that was displayed as part of thepreview of the first user interface operation is reversed when the firstuser interface operation is cancelled). Providing a preview of arearrangement or reordering operation in accordance with a hover-moveinput and determining whether to cancel the rearrangement or reorderingoperation depending on how the hove-move ends (e.g., by touching down onthe touch-sensitive surface or moving away from the touch-sensitivesurface) enhance the operability of the device and make the user-deviceinterface more efficient (e.g., by reducing the number of steps neededto cancel the rearrangement or reordering operation).

In some embodiments, confirming the first user interface operation inaccordance with a determination that the input object no longer meetsthe hover proximity criteria because the input object has made contactwith the touch-sensitive surface includes (1830): displaying the firstitem and the second item (and any other items in the list or grid) inthe user interface in a second configuration that is distinct from thefirst configuration (e.g., the list of items remains displayed in thesecond order that is distinct from the first order after lift-off of theinput object from the touch-sensitive surface is detected, and after theinput object is lifted out of the hover proximity range above thetouch-sensitive surface; the grid of application items remains displayedin the second configuration that is distinct from the firstconfiguration after lift-off of the input object from thetouch-sensitive surface is detected, and after the input object islifted out of the hover proximity range above the touch-sensitivesurface), e.g., as shown in FIG. 8H. Providing a preview of arearrangement or reordering operation in accordance with a hover-moveinput and determining whether to confirm the rearrangement or reorderingoperation depending on how the hover-move input ends (e.g., by touchingdown on the touch-sensitive surface or moving away from thetouch-sensitive surface) enhance the operability of the device and makethe user-device interface more efficient (e.g., by reducing the numberof steps needed to confirm the rearrangement or reordering operation).

In some embodiments, the operation to relocate the first item on thedisplay includes (1832) an operation to scroll the user interface as awhole, and updating the user interface to indicate a preview of thefirst user interface operation includes scrolling the user interface inthe display in accordance with the lateral movement of the input object(e.g., the whole user interface (including all of its content) moves inunison in accordance with the lateral hover movement of the inputobject). In some embodiments, the start of the first user interfaceoperation includes trigging of the scroll mode. In some embodiments,detecting the input by the input object that corresponds to a start ofthe first user interface operation includes detecting a contact by theinput object with the touch-sensitive surface at a location thatcorresponds to the user interface, and detecting that the contact ismaintained at the location for more than a first threshold amount oftime (e.g., detecting a tap-hold input directed to the user interface totrigger the scroll mode). In some embodiments, detecting the input bythe input object that corresponds to a start of the first user interfaceoperation includes detecting a contact by the input object with thetouch-sensitive surface at a location that corresponds to userinterface, and detecting that a characteristic intensity of the contactincreases above a first threshold intensity (e.g., detecting a lightpress input directed to the user interface to trigger the scroll mode).In some embodiments, detecting the input by the input object thatcorresponds to a start of the first user interface operation includesdetecting an in-air gesture by the input object (e.g., an in-air wigglegesture) at a hover location directly above the first item or the userinterface. In some embodiments, canceling the operation includesrestoring the user interface to a state before the scroll mode istriggered. In some embodiments, confirming the operation includes, afterthe input object is lifted out of the hover proximity range above thetouch-sensitive surface, maintaining the user interface in a state thatthe user interface has after the user interface has been scrolled inaccordance with the lateral hover movement of the input object.Providing a preview of a scroll operation in accordance with ahover-move input and determining whether to confirm the scroll operationdepending on how the hover-move input ends (e.g., by touching down onthe touch-sensitive surface or moving away from the touch-sensitivesurface) enhance the operability of the device and make the user-deviceinterface more efficient (e.g., by reducing the number of steps neededto confirm the scroll operation).

In some embodiments, the first user interface operation includes (1834)an operation to resize a selection object (e.g., a text selection box,or an object selection box), which includes an operation to relocate afirst boundary of the selection object on the display (while maintaininga location of a second boundary of the selection object on the display).Updating the user interface to indicate a preview of the user interfaceoperation includes adjusting selectable content that is included in theselection object by moving a first boundary of the selection objectwithin selectable content (e.g., selectable text) from the firstlocation to the second location in accordance with the lateral movementof the input object (e.g., moving an edge of a selection box, or movinga lollipop or selection handle on or near an edge of a selection box,from a first location to a second location in the user interface toadjust the content selection). This is illustrated in FIGS. 8P-8V, forexample. In some embodiments, if a new selection is initiated by theinput, the selection is started from the original location of a textselection cursor at the start of the lateral movement, and the selectionis expanded from the original location of the text selection cursor inaccordance with the lateral movement of the input object. In someembodiments, if an existing selection is re-engaged by the input (e.g.,one of the edges of the existing selection is selected by the inputobject), the lateral movement of the input object expands or contractsthe current selection in accordance with the lateral hover movement ofthe input object. Providing a preview of a resize operation on aselected object in accordance with a hover-move input and determiningwhether to confirm the resize operation depending on how the hover-moveinput ends (e.g., by touching down on the touch-sensitive surface ormoving away from the touch-sensitive surface) enhance the operability ofthe device and make the user-device interface more efficient (e.g., byreducing the number of steps needed to confirm the resize operation).

In some embodiments, cancelling the first user interface operation inaccordance with a determination that the input object no longer meetsthe hover proximity criteria because the input object has exited a hoverproximity range of the touch-sensitive surface includes (1836) ceasingto display the selection object or restoring the first boundary of theselection object to the first location (e.g., restoring the selectioncursor to the original location of the selection cursor within theselectable content, or restoring the first boundary of the selectionobject to the original location of the first boundary of the selectionobject within the selectable content) after detecting that the inputobject no longer meets the hover proximity criteria. This is illustratedin FIG. 8U-8V, where selection handle 838 is restored to its originallocation, for example. Providing a preview of a resize operation on aselection object in accordance with a hover-move input and determiningwhether to cancel the resize operation depending on how the hover-moveinput ends (e.g., by touching down on the touch-sensitive surface ormoving away from the touch-sensitive surface) enhance the operability ofthe device and make the user-device interface more efficient (e.g., byreducing the number of steps needed to cancel the resize operation).

In some embodiments, confirming the first user interface operation inaccordance with a determination that the input object no longer meetsthe hover proximity criteria because the input object has made contactwith the touch-sensitive surface includes (1838) maintaining display ofthe selection object with the first boundary of the selection object atthe second location that is distinct from the first location afterdetecting that the input object no longer meets the hover proximitycriteria (e.g., maintaining the location of the first boundary evenafter the input object is lifted off of the touch-sensitive surface andlifted out of the hover proximity range above the touch-sensitivesurface). This is illustrated in FIG. 8T, for example. In someembodiments, in response to detecting that the input object no longermeets the hover proximity criteria, the device displays options forinteracting with selected content corresponding to the selection object(e.g., cut, copy, paste, format as bold, format with underline, formatwith italics). Providing a preview of a resize operation on a selectionobject in accordance with a hover-move input and determining whether toconfirm the resize operation depending on how the hover-move input ends(e.g., by touching down on the touch-sensitive surface or moving awayfrom the touch-sensitive surface) enhance the operability of the deviceand make the user-device interface more efficient (e.g., by reducing thenumber of steps needed to confirm the resize operation on the selectionobject).

In some embodiments, while the input object meets hover proximitycriteria, the device detects (1840) that the input object meets firstcriteria (e.g., guidance provision criteria or alert generationcriteria), wherein the first criteria (e.g., the guidance provisioncriteria or alert generation criteria) include a requirement that theinput object is within a respective threshold range (e.g., distance) ofa boundary of the hover proximity range in order for the first criteriato be met (e.g., the first criteria are met when the input object iswithin a first threshold distance away from the upper boundary of thehover proximity range (e.g., when the input object is about to exit thehover proximity range of the touch-sensitive surface) or when the inputobject is within a second threshold distance away from thetouch-sensitive surface (e.g., when the input object is about to makecontact with the touch-sensitive surface)). In response to detectingthat the first criteria (e.g., the guidance provision criteria or alertgeneration criteria) are met the input object, the device providesfeedback (e.g., visual, audio, and/or haptic feedback) to indicate thatthe input object is within a respective threshold range (e.g., distance)of a boundary of the hover proximity range. Providing visual feedback toindicate that the input object is about to exit the hover proximityrange (e.g., to indicate that the hover input is about to end due tolift-off) enhances the operability of the device and makes theuser-device interface more efficient (e.g., by alerting the user oflikely changes in the state of the device and thereby helping the userto achieve an intended result by providing the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, providing feedback to indicate that the inputobject is within a respective threshold range of a boundary of the hoverproximity range includes (1842): in accordance with a determination thatthe input object meets the first criteria (e.g., guidance provisioncriteria) because the input object is within a first threshold distanceof an upper boundary of the hover proximity range of the touch-sensitivesurface, providing a preview of cancellation of the first user interfaceoperation (e.g., when the first user interface operation is a moveoperation for moving a first item in a user interface, visuallyhighlighting the original location of the first item in the userinterface if the input object were to exit the hover proximity rangenow). In some embodiments, the preview of the cancellation ceases to bedisplayed when the input object moves away from the boundary of thehover proximity range and continue to hover across the touch-sensitivesurface. Providing feedback to indicate that the input object is withina respective threshold range of a boundary of the hover proximity rangefurther includes: in accordance with a determination that the inputobject meets the first criteria (e.g., the guidance provision criteria)because the input object is within a second threshold distance of thetouch-sensitive surface, providing a preview of confirmation of thefirst user interface operation (e.g., when the first user interfaceoperation is a move operation for moving a first item in a userinterface, visually highlighting a final location of the first item inthe user interface if the input object were to make contact with thetouch-sensitive surface now). In some embodiments, the preview of theconfirmation ceases to be displayed when the input object moves awayfrom the touch-sensitive surface and continues to hover across thetouch-sensitive surface. Providing different visual feedback to indicatewhether the operation is about to be canceled or confirmed (e.g.,depending on whether the hover input is about to end due to lift-off ortouch-down of the input object) enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by alertingthe user of likely changes in the state of the device and therebyhelping the user to achieve an intended result by providing the requiredinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, providing feedback to indicate that the inputobject is within a respective threshold range of a boundary of the hoverproximity range includes (1844): providing an alert to a user toindicate that the input object will cease to meet the hover proximitycriteria if movement of the input object were to continue in a currentdirection toward or away from the touch-sensitive surface (e.g., whenthe first user interface operation is a move operation for moving afirst item in a user interface, visually highlighting the first item inthe user interface by enlarging the first item, and/or visuallyhighlighting a drop-off location for the first item (e.g., thedrop-location is the original location of the first item if the inputobject exits hover proximity range be moving away from thetouch-sensitive surface, and the drop-off location is the new finallocation of the first item if the input object exits hover proximityrange by making contact with the touch-sensitive surface), and/orproviding a tactile or audio output to indicate that the input objectwill cease to meet the hover proximity criteria if movement of the inputobject were to continue in a current direction toward or away from thetouch-sensitive surface). Providing visual feedback to indicate that theinput object is about to exit the hover proximity range (e.g., toindicate that the hover input is about to end due to lift-off ortouch-down of the input object) enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by alertingthe user of likely changes in the state of the device and therebyhelping the user to achieve an intended result by providing the requiredinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, providing the alert to the user includes (1846): inaccordance with a determination that the input object meets the firstcriteria (e.g., alert generation criteria) because the input object iswithin a first threshold distance of an upper boundary of the hoverproximity range of the touch-sensitive surface, changing an appearanceof the first item (e.g., when the first user interface operation is amove operation for moving a first item in a user interface, visuallyhighlighting the first item in the user interface). In some embodiments,the alert ceases to be displayed when the input object moves away fromthe boundary of the hover proximity range and continue to hover acrossthe touch-sensitive surface, or after the input object continues to movetoward the boundary of the hover proximity range and then exits thehover proximity range. Providing the alert to the user includes furtherincludes: in accordance with a determination that the input object meetsthe first criteria (e.g., the alert generation criteria) because theinput object is within a second threshold distance of thetouch-sensitive surface, highlighting a drop-off location for the firstitem in the user interface (e.g., when the first user interfaceoperation is a move operation for moving a first item in a userinterface, visually highlighting a final location of the first item inthe user interface if the input object were to make contact with thetouch-sensitive surface now). In some embodiments, the highlighting ofthe drop-off location for the first item ceases to be displayed when theinput object moves away from the touch-sensitive surface and continuesto hover across the touch-sensitive surface, or when the input objectmakes contact with the touch-sensitive surface. Providing differentvisual feedback (e.g., changing the appearance of the first item versushighlighting a drop-off location for the first item) depending onwhether the hover input is about to end due to lift-off or touch-down ofthe input object enhances the operability of the device and makes theuser-device interface more efficient (e.g., by alerting the user oflikely changes in the state of the device and thereby helping the userto achieve an intended result by providing the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

It should be understood that the particular order in which theoperations in FIGS. 18A-18G have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 1500, 1600, 1700, 1900, 2000, 2100, 2200, 2300, and 2400) arealso applicable in an analogous manner to method 1800 described abovewith respect to FIGS. 18A-18G. For example, the contacts, gestures,input objects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described above with reference to method 1800 optionally haveone or more of the characteristics of the contacts, gestures, inputobjects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described herein with reference to other methods describedherein (e.g., methods 1500, 1600, 1700, 1900, 2000, 2100, 2200, 2300,and 2400). For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 18A-18G are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, detection operations 1804 and 1810, updating operation 1806,and canceling operation and confirming operation 1812 and are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

FIGS. 19A-19E are flow diagrams illustrating a method 1900 ofinteracting with a user interface object through proximity-based andcontact-based inputs in accordance with some embodiments. The method1900 is performed at an electronic device (e.g., device 300, FIG. 3, orportable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the electronic deviceincludes one or more first sensors to detect proximity of an inputobject (e.g., a finger or a stylus) above the touch-sensitive surface(e.g., proximity sensors (such as infrared sensors), capacitive sensorsin the touch sensitive surface, or cameras next to the touch-sensitivesurface) and one or more second sensors to detect intensities of contactof the input object with the touch-sensitive surface. In someembodiments, the one or more second sensors are different from the oneor more first sensors. In some embodiments, the one or more secondsensors are the same as the one or more first sensors. In someembodiments, the touch-sensitive surface and the display are integratedinto a touch-sensitive display. In some embodiments, the display is atouch-screen display and the touch-sensitive surface is on or integratedwith the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 1900 are, optionally,combined and/or the order of some operations is, optionally, changed.

Method 1900 relates to a heuristic for determining whether to maintainor cancel currently displayed visual feedback. Specifically, after thedevice detects a predefined interaction with a first user interfaceobject by an input object, the device displays corresponding visualfeedback (e.g., display of a second user interface object) inassociation with the first user interface object. The device determineswhether to maintain or cancel the visual feedback (e.g., display of thesecond user interface object) depending on whether the input objectcontinues to hover over the touch-sensitive surface. In accordance withthe method described herein, the device maintains display of a transientuser interface object (e.g., the second user interface object) inaccordance with whether the input object continues to meet hoverproximity criteria. In other words, the transient user interface objectthat is displayed in response to the user interaction is neither a“sticky” object that needs to be subsequently dismissed by a separateinput, nor a conventional “non-sticky” object that ceases to bedisplayed immediately upon lift-off the contact that triggered thedisplay of the transient user interface object. Instead, the transientuser interface object remains displayed without any contact beingmaintained with the touch-sensitive surface (e.g., after lift-off of thecontact), and is dismissed when the input object ceases to hover overthe touch-sensitive surface (e.g., when the input object is lifted awayor makes contact with the touch-sensitive surface). As a result, thedevice is able to provide information and/or functionality (e.g., asembodied in the transient user interface object) to the user for as longas needed (e.g., as determined by the duration of the user input), andfor only as long as necessary (e.g., only until the user terminates thehover input). Providing such improved feedback and reducing the numberof steps to maintain or cancel currently displayed visual feedback inaccordance with the method described herein enhance the operability ofthe device and make the user-device interface more efficient (e.g., byhelping the user to achieve an intended result by providing the requiredinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduce power usage and improve battery lifeof the device (e.g., by enabling the user to use the device more quicklyand efficiently).

Device displays (1902) a first user interface object (e.g., applicationlaunch icon, list item, etc.) at a first location on the display. Thedevice detects (1904) a predefined interaction (e.g., a tap, a press, atouch and hold, a hover interaction, etc.) with the first user interfaceobject by the input object. In response to detecting the predefinedinteraction with the first user interface object by the input object,the device displays a second user interface object that is associatedwith the first user interface object (e.g., the second user interfaceobject is a preview, a tool-tip, a pop-up, an unread notification, acontrol (e.g., a radial menu or dial), or a quick action menu associatedwith the first user interface object (e.g., an application launch icon,an item in a list, etc.)). In some embodiments, the second userinterface object is concurrently displayed with the first user interfaceobject. In some embodiments, the second user interface object isoverlaid on the first user interface object and may partially obscurethe first user interface object. In some embodiments, when the seconduser interface object is displayed, portions of the user interface thatare not occupied by the first and second user interface objects aredeemphasized, e.g., blurred and/or darkened. While displaying the seconduser interface object, the device detects (1908) a change in a hoverproximity parameter of the input object (e.g., a hover distance of theinput object above the touch-sensitive surface or other equivalent oranalogous measure of the hover distance, such as capacitance, shadowcharacteristics, etc.). In response to detecting the change in the hoverproximity parameter of the input object: in accordance with adetermination that the input object meets continue-to-display criteria,wherein the continue-to-display criteria require that the input objectcontinues to meet hover proximity criteria (e.g., the hover proximitycriteria require that a hover proximity parameter (e.g., a parameterbased on hover distance) associated with the input object is less than athreshold proximity value (e.g., a threshold hover distance) in orderfor the hover proximity criteria to be met) in order forcontinue-to-display criteria to be met, the device maintains (1910)display of the second user interface object; and in accordance with adetermination that the input object meets cease-to-display criteria,wherein the cease-to-display criteria require that the input object nolonger meets the hover proximity criteria (e.g., because the inputobject has exited the hover proximity range above the touch-sensitivesurface) in order for the cease-to-display criteria to be met, thedevice ceases to display the second user interface object (e.g., whilemaintaining display of the first user interface object). This isillustrated in FIGS. 9E, 9F, 9I, 9N, and 9O, where mini applicationobject 912 and quick action menu 914 remain displayed when finger 734remains the hover proximity range above the touch-screen, and cease tobe displayed when finger 734 is lifted out of the hover proximity rangeabove the touch-screen, for example.

In some embodiments, in response to detecting the change in the hoverproximity parameter of the input object: in accordance with adetermination that the input object meets activate-function criteria,wherein the activate-function criteria require that the input objectmakes contact with the touch-sensitive surface in order for theactivate-function criteria to be met, the device activates (1912) afunction associated with the second user interface object (e.g.,displaying full content associated with the preview, expanding thetool-tip to show a help page related to the tool tip, opening a webpageassociated with the pop-up, display a communication corresponding to theunread notification, highlighting a current value or adjusting a currentvalue of the control (e.g., a radial menu or dial), or selecting a menuoption in the quick action menu associated with the first user interfaceobject (e.g., an application icon, an item in a list, etc.))). This isillustrated in FIGS. 12M-12N and 12Q-12R, for example, where a menuoption in quick action menu 1230 is activated by contact 1234. In someembodiments, in accordance with a determination that the second userinterface object is no longer displayed, and that the input object hasmade the contact with the touch-sensitive surface after it had exitedthe hover proximity range first, launch the application that correspondsto the first user interface object (if the first user interface objectis an application icon) or open the first user interface object todisplay/playback content of the first user interface object (e.g., ifthe first user interface object is an item such as an email item, or aweather item, a media item, etc.). In some embodiments, theactivate-function criteria further requires that a characteristicintensity of the contact by the input object exceeds a first intensitythreshold in order for the activate-function criteria to be met. In someembodiments, the activate-function criteria further requires that thecontact by the input object be maintained for more than a thresholdamount of time with less than a threshold amount of movement in orderfor the activate-function criteria to be met. Maintaining display of asecond user interface object while hover proximity criteria are met andactivating a function associated with the second user interface objectwhen the input object ceases to meet the hover proximity criteria bymaking contact with the touch-sensitive surface enhance the operabilityof the device and make the user-device interface more efficient (e.g.,by reducing the number of steps needed to activate a function associatedwith the second user interface object after lift-off of the contact isalready detected) which, additionally, reduce power usage and improvebattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, maintaining display of the second user interfaceobject in accordance with a determination that the input object meetsthe continue-to-display criteria includes (1914) dynamically changing anappearance of the second user interface object (e.g., dynamicallyadjusting a size, hue, opacity, and/or other visual property of thesecond user interface object) in accordance with a characteristic valueof the hover proximity parameter of the input object (e.g., as the inputobject moves away from the touch-sensitive surface, the second userinterface object increases in size and increases in opacity, and as theinput object moves toward the touch-sensitive surface, the second userinterface object decreases in size and decreases in opacity). This isillustrated in FIGS. 9F, 9I, and 9J, for example. Dynamically adjustingthe visual feedback (e.g., adjusting the appearance of the second userinterface object) in accordance with a current hover proximity parameterof the input object enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended result by providing the required inputs and reducinguser mistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice (e.g., by enabling the user to use the device more quickly andefficiently).

In some embodiments, detecting the predefined interaction with the firstuser interface object includes (1916) detecting a first change in thehover proximity parameter of the input object in a first direction(e.g., monotonically increasing or decreasing within the hover proximityrange before touch-down of the input object), and displaying the seconduser interface object includes: displaying a precursor image of thesecond user interface object; and dynamically changing an appearance ofthe precursor image of the second user interface object in a firstmanner in accordance with the first change in the hover proximityparameter of the input object. For example, as the input object is firstdetected within the hover proximity range above the touch-sensitivesurface over the first user interface object, a precursor image of thesecond user interface object is displayed (e.g., a preview platteremerges from behind the first user interface object); and as the inputobject moves closer to the touch-sensitive surface, the precursor imagegrows in size in accordance with the decreasing hover proximityparameter of the input object (e.g., more of the preview platter isrevealed from behind the first user interface object as the input objectmoves closer to the touch-sensitive surface). This is illustrated inFIGS. 9A-9B and FIGS. 12B-12C, for example. Displaying a preview of thesecond user interface object (e.g., precursor image) and dynamicallyadjusting the appearance of the preview in accordance with the changingproximity parameter of the input object during a hovering-in process ofthe input object enhance the operability of the device and make theuser-device interface more efficient (e.g., by providing an indicationof the internal state of the device and helping the user to achieve anintended result by providing the required inputs and reduce usermistakes when operating/interacting with the device) which,additionally, reduce power usage and improve battery life of the device(e.g., by enabling the user to use the device more quickly andefficiently).

In some embodiments, dynamically changing the appearance of the seconduser interface object in accordance with the characteristic value of thehover proximity parameter of the input object includes (1918): inaccordance with detection of a second change in the hover proximityparameter of the input object in the first direction that is identicalto the first change (e.g., monotonically increasing or decreasing withinthe hover proximity range after the touch-down of the input object),dynamically changing the appearance of the second user interface objectin a second manner in accordance with the second change in the hoverproximity parameter of the input object, wherein the second manner isdifferent from the first manner. For example, when the input objectmoves towards the touch-sensitive surface and enters the hover proximityrange initially, the preview of the second user interface object is ashadow image of the second user interface object that gradually expandsfrom behind the first user interface object (and becomes brighter, andmore saturated) as the input object continues to move closer to thetouch-sensitive surface, and eventually pops out to become the seconduser interface object when the input object makes contact with andpresses against the touch-sensitive surface. When the input object thenmoves away from the touch-sensitive surface, the second user interfaceobject is maintained on the display and becomes grows in size andbecomes more transparent; and if the input object approaches thetouch-sensitive surface again, the second user interface object shrinksin size and becomes more opaque. In other words, the user interfacebehaves differently to the same changes in hover proximity parameter ofthe input object before and after the input object makes contact withthe touch-sensitive surface. This is illustrated in FIG. 9J, forexample. Displaying different dynamic visual feedback (e.g., changingthe appearance of a preview of the second user interface object duringhovering in and changing the appearance of the second user interfaceobject during hover out) in accordance with the changing proximityparameter of the input object for the hovering-in and hovering outprocesses enhance the operability of the device and make the user-deviceinterface more efficient (e.g., by providing an indication of theinternal state of the device and helping the user to achieve an intendedresult by providing the required inputs and reduce user mistakes whenoperating/interacting with the device) which, additionally, reduce powerusage and improve battery life of the device (e.g., by enabling the userto use the device more quickly and efficiently).

In some embodiments, the continue-to-display criteria require (1920)that a first characteristic rate of change in the hover proximityparameter of the input object (e.g., the rate of change immediatelyafter lift-off of the input object from the touch-sensitive surface)after the second user interface object is displayed is less than a firstthreshold rate (and/or the input object is maintained in a hover rangefor less than a first threshold amount of time after detecting thepredefined interaction) in order for the continue-to-display criteria tobe met. For example, if the first rate of change is fast (e.g., theinput object is quickly lifted away from the touch-sensitive surface),the device does not maintain display of the second user interface objecteven during the brief moment that the input object is still within thehover proximity range above the touch-sensitive surface. If the firstrate of change is slow (e.g., the input object is gradually lifted awayfrom the touch-sensitive surface), the second user interface object iscontinually displayed while the input object is hovering within thehover proximity range of the touch-sensitive surface. In other words, aquick lift-off of the input object causes the device to skip thetransient display of the second user interface object after lift-off ofthe contact by the input object, and a slow, more deliberate lift-off ofthe input object causes the device to provide the transient display ofthe second user interface object after lift-off of the contact by theinput object. This is illustrated in FIGS. 9K-9M, for example. Skippingdisplay of the transient user interface object (e.g., the second userinterface object) when the input object is quickly lifted away from theuser interface object enhances the operability of the device and makesthe user-device interface more efficient (e.g., by avoiding unnecessaryvisual feedback and reducing user confusion, and by helping the user toachieve an intended result by providing the required inputs and reducinguser mistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice (e.g., by enabling the user to use the device more quickly andefficiently).

In some embodiments, the cease-to-display criteria require (1922) that asecond characteristic rate of change in the hover proximity parameter ofthe input object (e.g., the rate of change when approaching the upperboundary of the hover proximity range above the touch-sensitive surface)after the second user interface object is displayed is greater than asecond threshold rate (e.g., in some embodiments, the second thresholdrate is the same as the first threshold rate. In some embodiments, thesecond threshold rate is different from the first threshold rate)(and/or the input object is maintained in a hover range for more than asecond threshold amount of time after detecting the predefinedinteraction that is optionally different from or the same as the firstthreshold amount of time) in order for the cease-to-display criteria tobe met. For example, if the second rate of change is fast (e.g., theinput object is quickly lifted out of the hover proximity range, thedevice immediately ceases to display the second user interface objectwhen the input object exits the hover proximity range above thetouch-sensitive surface. If the second rate of change is slow (e.g., theinput object is gradually lifted out of the hover proximity range), thesecond user interface object is continually displayed for a brief momentafter the input object is outside of the hover proximity range above thetouch-sensitive surface, before the device completely ceases to displaythe second user interface object. In other words, a quick lift-off ofthe input object causes the device to quickly remove the second userinterface object from the display after the input object exits the hoverproximity range, and a slow, more deliberate lift-off of the inputobject causes the device to provide a lingering, transient display ofthe second user interface after the input object has exited the hoverproximity range. This is illustrated in FIGS. 9N-9O, for example. Insome embodiments, an animation showing the second user interface objectbeing pulled away from the z-plane the user interface and then bouncingback toward the z-plane of the user interface is displayed after theinput object has exited the hover proximity range. Allowing thetransient user interface object to linger after the input object hasbeen lifted out of the hover proximity range above the touch-sensitivesurface if the input object is lifted slowly out of the hover proximityrange enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by allowing the user more time to reviewand consider the second user interface object, helping the user toachieve an intended result by providing the required inputs, andreducing user mistakes when operating/interacting with the device).

In some embodiments, while the input object meets thecontinue-to-display criteria and while maintaining display of the seconduser interface: the device detects (1924) a third change in the hoverproximity parameter of the input object from a first value to a secondvalue (e.g., when the input object moves away from the touch-sensitivesurface while still remaining within the hover proximity range). Inresponse to detecting the first change in the hover proximity parameter,the device applies a first visual change to an appearance of the seconduser interface object (e.g., changing (e.g., discretely or,alternatively, dynamically) the transparency or opacity of the seconduser interface object from a first transparency value to a secondtransparency or opacity value, or changing (e.g., discretely or,alternatively, dynamically) the color saturation of the second userinterface object from a first saturation value to a second saturationvalue). After applying the first visual change to the appearance of thesecond user interface object, the device detects a second change in thehover proximity parameter of the input object from the second value tothe first value (e.g., when the input object moves toward thetouch-sensitive surface while still remaining within the hover proximityrange). In response to detecting the second change in the hoverproximity parameter of the input object, the device reverses the firstvisual change to the appearance of the second user interface object. Forexample, when the input object moves toward the touch-sensitive surfaceagain without first exiting the hover proximity range, the changes madeto the appearance of the second user interface object is reverted. Insome embodiments, the second user interface is completely restored whenthe input object makes contact with the touch-sensitive surface for asecond time since the initial display of the second user interfaceobject. Allowing the transient user interface object (e.g., the seconduser interface object) to linger after the input object has been liftedout of the hover proximity range above the touch-sensitive surface ifthe input object is lifted slowly out of the hover proximity rangeenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by allowing the user more time to reviewand consider the second user interface object, helping the user toachieve an intended result by providing the required inputs, andreducing user mistakes when operating/interacting with the device).

In some embodiments, detecting the predefined interaction with the firstuser interface object by the input object includes (1926): detecting afirst input by a first contact (made by the input object with thetouch-sensitive surface) at a location on the touch-sensitive surfacethat corresponds to the first user interface object on the display, anddetecting that the first input meets object-display criteria, whereinthe object-display criteria require that a characteristic intensity ofthe first contact exceeds a first intensity threshold (e.g., a lightpress intensity threshold) in order for the object-display criteria tobe met. This is illustrated in FIGS. 9C-9E, for example. Requiring apress input to trigger display of the transient user interface object(e.g., the second user interface object) enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byavoiding accidental display of the second user interface object, helpingthe user to achieve an intended result by providing the required inputs,and reducing user mistakes when operating/interacting with the device).

In some embodiments, the first user interface object corresponds (1928)to an application (e.g., the first user interface object is anapplication launch icon that is displayed on a home screen, and a tapinput detected on the application launch icon launches the application),the second user interface object includes a menu of options (e.g., miniapplication object 912 or quick action menu 914 in FIG. 9E) that areconfigured to cause performance a subset of functions of the application(e.g., the second user interface object is a quick action menuassociated with an application that is displayed when a user press on anapplication icon corresponding to the application). Requiring a pressinput to trigger display of a quick action menu enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by avoiding accidental display of the quick action menu and reducinguser mistakes when operating/interacting with the device). Additionally,displaying a quick action menu as a transient user interface object thatcan be maintained or dismissed depending on whether the input objectcontinues to hover over the touch-sensitive surface or is lifted out ofthe hover proximity range enhances the operability of the device andmakes the user-device interface more efficient (e.g., by reducing thenumber of inputs needed to perform an operation (e.g., to activate amenu function or dismiss the menu)) which, additionally, reduces powerusage and improves battery life of the device by enabling the user touse the device more quickly and efficiently.

In some embodiments, the first user interface object corresponds (1930)to a content item (e.g., the first user interface object is a list item(e.g., song, weather, news, email, message, conversation, contact, etc.)in a list (e.g., playlist, weather list, news list, email list, messagelist, conversation list, contact list, etc.)), and the second userinterface object is a preview of the content item (e.g., the previewshows an abridged or reduced scale version of the content item). In someembodiments, a tap input detected on the first user interface objectopens the content item without showing the preview of the content item.Requiring a press input to trigger display of a preview of a contentitem enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by avoiding accidental display of thepreview and reducing user mistakes when operating/interacting with thedevice). Additionally, displaying a preview of a content item as atransient user interface object that can be maintained or dismisseddepending on whether the input object continues to hover over thetouch-sensitive surface or is lifted out of the hover proximity rangeenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by reducing the number of inputs neededto perform an operation (e.g., to display the preview or dismiss thepreview)) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, while the preview of the content item is displayed,the device detects (1932) a second input by the input object, includingdetecting a second contact (e.g., the second contact is the same as thefirst contact that is continuously maintained on the touch-sensitivesurface, or a separate contact from the first contact) by the inputobject at a location on the touch-sensitive surface that corresponds tothe preview. In response to detecting the second input by the inputobject: in accordance with a determination that the second input meetsitem-open criteria, wherein the item-open criteria required that acharacteristic intensity of the second contact exceeds a secondintensity threshold (e.g., the second intensity threshold is the same asthe first intensity threshold, or is another intensity threshold that isdifferent from the first intensity threshold) in order for the item-opencriteria to be met (e.g., another light press input or a deep pressinput is required for the item-open criteria to be met), the deviceceases to display the preview and opening the content item. In someembodiments, when the preview is no longer displayed, the transientpreview is not displayed when the input object is lifted off thetouch-sensitive surface and hovers over the touch-sensitive surfacewithin the hover proximity range; instead, the fully opened content itemremains displayed on the display. In some embodiments, a swipe on thepreview causes display of options associated with the preview. Forexample, in response to detecting the second input by the input object:in accordance with a determination that the second input meetsoption-display criteria, wherein the option-display criteria requirethat a movement of the second contact (e.g., in a predetermineddirection) exceeds a threshold distance across the touch-sensitivesurface in order for the option-display criteria to be met (e.g., aswipe input is required for the option-display criteria to be met), thedevice displays one or more options associated with the content itemwhile maintaining display of the preview (e.g., one or more options,such as save, share, copy, delete, etc. are displayed with the previewonce the preview is swiped upward or sideways). Requiring a deep pressinput to fully open a content item enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byavoiding accidental open the content item and reducing user mistakeswhen operating/interacting with the device). Additionally, allowing theuser to press harder on the preview to open the content item or to hoverabove the preview to maintain display of the preview enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by reducing the number of inputs needed to perform anoperation (e.g., to open the item or maintaining the preview), andproviding additional functionality without cluttering the user interfacewith additional displayed controls) which, additionally, reduces powerusage and improves battery life of the device by enabling the user touse the device more quickly and efficiently.

In some embodiments, before detecting the first contact by the inputobject with the touch-sensitive surface, the device detects (1934) thatthe input object meets intensity-reaction-hint criteria, wherein theintensity-reaction-hint criteria require that the input object is withina hover proximity range of the touch-sensitive surface, and that thefirst user interface object is an intensity-reactive object (e.g., thedevice provides different object-specific reactions when the first userinterface object is activated by a contact with a first intensity versusa contact with a second intensity that is different from the firstintensity, in other words, the first user interface object hasdifferentiated object-specific responses to intensity-based inputs(e.g., touch inputs with different intensities)). In response todetecting that the input object meets the intensity-reaction-hintcriteria, the device displays a first visual effect to indicate that thefirst user interface object is intensity-reactive. For example, in someembodiments, the device displays a shadow platter behind the first userinterface object that expands or contracts in accordance with thecurrent hover proximity parameter of the input object. In someembodiments, the device further dims the portions of the user interfacesurrounding the first user interface object when the device determinesthat the intensity-reaction-hint criteria are met by the input object.In some embodiments, the device visually highlights or enlarges thefirst user interface object to indicate that the first user interfaceobject is intensity-reactive. In contrast, for a user interface objectthat is not intensity-reactive, when the input object is hovering withina hover proximity range of the touch-sensitive surface above the userinterface object on the display, the intensity-reaction-hint criteriawill not be met, and the device forgoes displaying any of the abovevisual effects. In some embodiments, the first user interface object isan application icon and the intensity-based response for a press inputis displaying a quick-action menu, in contrast to launching anapplication in response to a tap input. In some embodiments, theintensity-reaction-hint criteria are met when the input object isdetected within the hover proximity range above other types of userinterface objects that have other types of intensity-based responses.For example, in some embodiments, the first user interface object is alist item that corresponds to a content item, and the intensity-basedresponse is to display a preview of the content item when a user presseson the list item, in contrast to opening the list item in response to atap input. In some embodiments, in addition to providing visual feedbackto indicate whether a user interface object is intensity reactive inresponse to detecting the input object within hover proximity range ofthe object, the device also optionally provides haptic and/or feedbackto further enhance or facilitate the visual feedback. Additional detailsare described with respect to FIGS. 12A-12R and method 2200. Providingvisual feedback to indicate whether an object has differentiated,object-specific responses to intensity-based inputs (e.g., a light pressinput versus a deep press input) when an input object hovers over theobject enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by alerting the user of the nature andbehavior of the object, avoiding accidentally triggering anintensity-based response by making contact with the touch-sensitivesurface, helping the user to achieve an intended result by providing therequired inputs, and reducing user mistakes when operating/interactingwith the device) which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, the first user interface object corresponds (1936)to an application (e.g., the first user interface object is anapplication launch icon that is displayed on a home screen), and thesecond user interface object is an unread notification or a preview of acommunication for the application. Detecting the predefined interactionincludes: detecting that the input object meets notification-displaycriteria, wherein the notification-display criteria require that theinput object is within a hover proximity range of the touch-sensitivesurface, and that the application has at least one unread notificationor unread communication available for user review (e.g., the applicationicon has an indicator specifying the number of unread notifications orcommunications that are available for user's review, and/or anotification has been presented once and has been stored in thenotification center waiting for the user to process (e.g., discard,save, view, etc.)) in order for the notification-display criteria to bemet; and in response to detecting that the input object meets thenotification-display criteria, displaying the unread notification or thepreview of the communication without launching the application. Forexample, in some embodiments, the notification banner is displayed againover the user interface or near the first user interface object. In someembodiments, the notification continues to be displayed until the userlifts the input object out of the hover proximity range. This isillustrated in FIGS. 11A-11G, for example. Triggering display of anunread notification or communication that correspond to an applicationwhen an input object is detected to hover over an application launchicon of the application and maintaining display of the unreadnotification or communication for an amount of time that is determinedby how long the input object remains hovering over the touch-sensitivesurface enhance operability of the device and make the user-deviceinterface more efficient (e.g., by dynamically adapting the duration ofinformation presentation to user's input, and reducing the number ofsteps needed to display useful information and to dismiss the display ofthe information) which, additionally, reduce power usage and improvebattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, the first user interface object is (1938) a controlobject (e.g., the first user interface object is an application launchicon that is displayed on a home screen or a control that is displayedin a user interface) and the second user interface object is aninformation object (e.g., a tool-tip pop-up) that includes informationrelated to a function of the control object. Detecting the predefinedinteraction includes: detecting that the input object meetsinformation-display criteria, wherein the information-display criteriarequire that the input object is within a hover proximity range of thetouch-sensitive surface, and that an information object corresponding tothe first user interface object is available for user review (e.g., thecontrol has a tool tip) in order for the information-display criteria tobe met; and in response to detecting that the input object meets theinformation-display criteria, displaying the information object thatcorresponds to the first user interface object. For example, in someembodiments, the tool tip is displayed near the first user interfaceobject. In some embodiments, the tool-tip continues to be displayeduntil the user lifts the input object out of the hover proximity range.Triggering display of an information object (e.g., a tool tip) thatcorrespond to a user interface control when an input object is detectedto hover over the user interface control and maintaining display of theinformation object for an amount of time that is determined by how longthe input object remains hovering over the touch-sensitive surfaceenhance operability of the device and make the user-device interfacemore efficient (e.g., by dynamically adapting the duration ofinformation presentation to user's input, and reducing the number ofsteps needed to display useful information and to dismiss the display ofthe information) which, additionally, reduce power usage and improvebattery life of the device by enabling the user to use the device morequickly and efficiently.

It should be understood that the particular order in which theoperations in FIGS. 19A-19E have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 1500, 1600, 1700, 1800, 2000, 2100, 2200, 2300, and 2400) arealso applicable in an analogous manner to method 1900 described abovewith respect to FIGS. 19A-19E. For example, the contacts, gestures,input objects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described above with reference to method 1900 optionally haveone or more of the characteristics of the contacts, gestures, inputobjects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described herein with reference to other methods describedherein (e.g., methods 1500, 1600, 1700, 1800, 2000, 2100, 2200, 2300,and 2400). For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 19A-19E are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, detection operations 1904 and 1908, and maintaining operationand ceasing operation 1910 are, optionally, implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

FIGS. 20A-20I are flow diagrams illustrating a method 2000 ofinteracting with a user interface object through proximity-based andcontact-based inputs in accordance with some embodiments. The method2000 is performed at an electronic device (e.g., device 300, FIG. 3, orportable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the electronic deviceincludes one or more first sensors to detect proximity of an inputobject (e.g., a finger or a stylus) above the touch-sensitive surface(e.g., proximity sensors (such as infrared sensors), capacitive sensorsin the touch sensitive surface, or cameras next to the touch-sensitivesurface) and one or more second sensors to detect intensities of contactof the input object with the touch-sensitive surface. In someembodiments, the one or more second sensors are different from the oneor more first sensors. In some embodiments, the one or more secondsensors are the same as the one or more first sensors. In someembodiments, the touch-sensitive surface and the display are integratedinto a touch-sensitive display. In some embodiments, the display is atouch-screen display and the touch-sensitive surface is on or integratedwith the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 2000 are, optionally,combined and/or the order of some operations is, optionally, changed.

Method 2000 relates to providing multiple levels of distinct andnon-continuous visual feedback in response to variations in ahover-proximity parameter (e.g., hover distance) of an input objectwhile the input object hovers over the touch-sensitive surface.Specifically, the device recognizes at least two hover-proximity ranges,one of which being a sub-range of the other. When the input objectinitially moves toward the touch-sensitive surface, the input objectfirst enters a level-1 hover-proximity range while remaining outside ofa level-2 hover proximity range; and as the input object continues tomove closer to the touch-sensitive surface, the input object then entersthe level-2 hover proximity range while remaining within the level-1hover proximity range. Crossing the boundaries into the level-1 hoverproximity range and the level-2 hover proximity range triggers twodistinct responses that are discrete from each other in form and arerelated to each other in function and/or content. Segmenting the hoverrange above the touch-sensitive surface into multiple sub-ranges andusing different sub-ranges for triggering different visual feedback thatcorrespond to respective functions (including changing a state of thedevice in different respective manners and/or providing information ofdifferent respective types) allow the device to provide moredifferentiated and fine-tuned feedback to the user and allow the user toadjust his/her inputs after the inputs have been started to achievedesired results. Providing such improved feedback enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to achieve an intended result byproviding the required inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device (e.g., by enablingthe user to use the device more quickly and efficiently).

The device displays (2002) a first user interface on the display. Whiledisplaying the first user interface on the display (e.g., a media playeruser interface in a full screen mode, or a window of an application on abackground user interface (e.g., a desktop)), the device detects (2004)that first hover proximity criteria are met by the input object, whereinthe first hover proximity criteria require that a current value of ahover proximity parameter of the input object is within a first valuerange in order for the first hover proximity criteria to be met (e.g.,input object is less than 0.8 cm above the touch-sensitive surfacewithout touching the touch-sensitive surface). In response to detectingthat the first hover proximity criteria are met by the input object, thedevice displays (2006) first visual feedback (e.g., displaying a firstuser interface object (e.g., a playback control panel that was notpreviously displayed) concurrently with the first user interface (e.g.,overlaid on the first user interface)) that is associated with the firsthover proximity criteria. While displaying the first visual feedbackthat is associated with the first hover proximity criteria (e.g., whiledisplaying the first user interface object (e.g., the playback controlpanel)), the device detects (2008) a change in the current value of thehover proximity parameter of the input object and that second hoverproximity criteria are met by the input object after the change, whereinthe second hover proximity criteria require that the current value ofthe hover proximity parameter of the input object is within a secondvalue range that is within the first value range in order for the secondhover proximity criteria to be met (e.g., the input object is less than0.5 cm above the touch-sensitive surface without touching thetouch-sensitive surface) (in other words, the second hover proximitycriteria are more difficult to meet than the first hover proximitycriteria, and when the second hover proximity criteria are met, thefirst hover proximity criteria are also met, but not vice versa). Inresponse to detecting that the second hover proximity criteria are metby the input object, the device displays second visual feedback,distinct and non-continuous from the first visual feedback, that isassociated with the second hover proximity range (e.g., altering anappearance of a respective sub-element of the two or more sub-elementsin the first user interface object (e.g., highlighting the playbackbutton in the playback control panel that is directly under thefingertip), or augmenting the first visual feedback by adding additionalelements or abruptly/discretely altering one or more visualcharacteristics of the first visual feedback upon detecting that thesecond hover proximity criteria are met by the input object). This isillustrated in FIGS. 10A-10E, where tool bar 1006 is displayed whenfirst hover proximity criteria are met, and control affordance 1008 ishighlighted when second hover proximity criteria are met, for example.This is also illustrated in FIGS. 10F-10M, where control panel 1023 isdisplayed when first hover proximity criteria are met, and playbackcontrols 1024 and 1026 are highlighted respectively when second hoverproximity criteria are met (and finger 734 is near each of playbackcontrols 1024 and 1026), for example. This is also illustrated in FIGS.10O-10P, where respective counts of unread notifications for one or moreapplications in a folder are displayed (e.g., in notification list 1048)when first hover proximity criteria are met, and notification contentfor the unread notifications are displayed (e.g., in expandednotification list 1050) when second hover proximity criteria are met,for example. This is also illustrated in FIGS. 10T-10Y, where cursor1074 is displayed when first hover proximity criteria are met, andselection handles 1084 and 1086 are displayed when second hoverproximity criteria are met, for example. In some embodiments, the firstvisual feedback ceases to be displayed when the second hover proximitycriteria are met. In some embodiments, the first visual feedbackcontinues to be displayed when the second hover proximity criteria aremet and the second visual feedback is displayed. In some embodiments,one or more additional hover proximity criteria are used to triggeradditional device/user interface behaviors. For example, the differentembodiments described herein may be combined to have a three-levelproximity user interface, four-level proximity user interface, and soon. In some embodiments, for a particular level of hover proximitycriteria, the effect of meeting the proximity criteria at a first levelin one embodiment may take place concurrently with the effect of meetingproximity criteria at the same level or a different level in anotherembodiment described herein.

In some embodiments, while displaying the second visual feedback, thedevice detects (2012) that action-trigger criteria are met by the inputobject, wherein the action-trigger criteria require that the inputobject makes contact with the touch-sensitive surface in order for theaction-trigger criteria to be met. In some embodiments, theaction-trigger criteria further require lift-off of the input objectfrom the touch-sensitive surface in order for the action-triggercriteria to be met, such as a tap input. In response to detecting thatthe action-trigger criteria are met by the input object, the deviceinitiates performance of an action that corresponds to the second userinterface object (and ceasing to display the first visual feedback andthe second visual feedback, if either or both are still displayed). Thisis illustrated in FIGS. 10D-10E, where a tap input activates controlaffordance 1008, for example. This is also illustrated in FIGS. 10K-10L,where a tap input toggles playback control 1026, for example. This isalso illustrated in FIGS. 10R-10S, wherein a tap input launches aninstant messaging application to a user interface that corresponds to anunread notification that is tapped on, for example. The triggering ofthe action by contact after the second visual feedback is displayed inresponse to the second hover proximity criteria being met enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by providing additional information or functionalityand allowing the user to act upon the information or functionality witha natural progression of the current input gesture (e.g., continuing tomove closer to the touch-sensitive surface), and by helping the user toachieve an intended result by providing the required inputs and reducinguser mistakes when operating/interacting with the device).

In some embodiments, in response to detecting that the second hoverproximity criteria are met by the input object, the device ceases (2014)to display the first visual feedback when displaying the second visualfeedback. While displaying the second visual feedback, the devicedetects that the second hover proximity criteria are no longer met andthat the first hover proximity criteria are still met. In response todetecting that the second hover proximity criteria are no longer met andthat the first hover proximity criteria are still met: the device ceasesto display the second visual feedback that is associated with the secondhover proximity criteria; and the device redisplays the first visualfeedback that is associated with the first hover proximity criteria (ordisplaying a modified (e.g., reversed) version of the first visualfeedback in accordance with the changes of the hover proximity parameterof the input object after the input object has moved out of the secondhover proximity range but is still within the first hover proximityrange). Ceasing to display the first visual feedback when the secondhover proximity criteria are met (e.g., during a hover-in process by theinput object) helps to reduce visual clutter and avoid user confusionwhen providing inputs, and redisplaying the first visual feedback whenthe second hover proximity criteria are no longer met and the firsthover proximity criteria are still met (e.g., during the hover-outprocess by the input object) helps to reduce the number of steps toredisplay previously displayed information, both of which enhance theoperability of the device and make the user-device interface moreefficient (e.g., by reducing the number of steps needed to perform atask, helping the user to achieve an intended result by providing therequired inputs, and reducing user mistakes when operating/interactingwith the device).

In some embodiments, in response to detecting that the second hoverproximity criteria are met by the input object, the device maintains(2016) display of the first visual feedback while displaying the secondvisual feedback. While displaying the first visual feedback and thesecond visual feedback, the device detects that the second hoverproximity criteria are no longer met and that the first hover proximitycriteria are still met. In response to detecting that the second hoverproximity criteria are no longer met and that the first hover proximitycriteria are still met: the device ceases to display the second visualfeedback that is associated with the second hover proximity criteria;and the device continues to maintain display of the first visualfeedback that is associated with the first hover proximity criteria.This is illustrated in FIGS. 10F-10I and 10L, for example. Maintainingdisplay of the first visual feedback when the second hover proximitycriteria are met (e.g., during a hover-in process by the input object)helps to provide context for subsequent inputs and the second visualfeedback, and ceasing to display the second visual feedback when thesecond hover proximity criteria are no longer met (e.g., during thehover-out process by the input object) helps to reduce visual clutterand avoid user confusion, both of which enhance the operability of thedevice and make the user-device interface more efficient (e.g., byhelping the user to achieve an intended result by providing the requiredinputs, and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduce power usage and improve battery lifeof the device by enabling the user to use the device more quickly andefficiently.

In some embodiments, displaying the second visual feedback that isassociated with the second hover proximity range includes (2018)applying a first visual change to a first portion of the first userinterface while the input object is detected at a first hover locationabove the touch-sensitive surface (e.g., based on the first portion ofthe first user interface being closer to the first hover location of theinput object than other portions of the first user interface). While thefirst visual change is applied to the first portion of the first userinterface, the device detects a first movement (e.g., including alateral movement) of the input object from a first hover location to asecond hover location while the input object continues to meet thesecond hover proximity criteria (or, in some embodiments, the firsthover proximity criteria). In response to detecting the first movementof the input object while the input object continues to meet the secondhover proximity criteria (or, in some embodiments, the first hoverproximity criteria): the device, optionally, ceases to apply the firstvisual change to the first portion of the first user interface, and thedevice applies a second visual change to a second portion of the firstuser interface that is distinct from the first portion while the inputobject is detected at the second hover location above thetouch-sensitive surface (e.g., based on the second portion of the firstuser interface being closer to the second hover location of the inputobject than other portions of the first user interface). This isillustrated in FIGS. 10I-10J, where different control affordances 1024and 1026 are highlighted when finger 734 moves laterally near each ofthe two control affordances while continuing to meet the second hoverproximity criteria. Allowing the user to interact with (e.g., causingvisual changes that indicate the changes in the internal state of thedevice) different portions of the user interface during movement of theinput object while the input object continues to meet the second hoverproximity criteria and providing visual feedback indicating whichportion of the user interface is activated or will be activated uponcontact enhance the operability of the device and make the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended result by providing the required inputs and reduce usermistakes when operating/interacting with the device) which,additionally, reduce power usage and improve battery life of the device(e.g., by enabling the user to use the device more quickly andefficiently).

In some embodiments, displaying the first visual feedback that isassociated with the first hover proximity criteria includes (2020):shifting first content that is displayed on the display laterally acrossthe display (e.g., shifting content within the first user interface orshifting the entire first user interface from a first portion of displayto a second portion of the display) (and, optionally, displaying a thirduser interface object (e.g., a pull-tab for a control panel) at a thirdlocation on the display that is previously occupied by the first contentbefore the shifting of the first content). Displaying the second visualfeedback that is associated with the second hover proximity criteriaincludes, while the first content remains shifted, displaying a userinterface object (e.g., the control panel) (e.g., overlaid on the firstuser interface) at a location on the display that is previously occupiedby the first content. This is illustrated in FIGS. 10A-10C, where webcontent shifts up to make room for control bar 1006, for example. Insome embodiments, the user interface object is displayed as soon as thefirst content is shifted, without requiring the input object to hovercloser. In some embodiments, the user interface object is a tab orindicator that is pulled by a contact to bring in a control panel thatis overlaid on the first content. In some embodiments, the first contentincludes activatable control(s) or link(s) below the hover location ofthe input object, and upon the input object meeting the first hoverproximity criteria, the first content is shifted such that noactivatable control or links are below the hover location of the inputobject. In some embodiments, a pull tab is displayed below the hoverlocation of the input object that was previously occupied by theactivatable control(s) or link(s) of the first content, and a user canswipe or tap on the pull tab to bring up a control panel over the firstcontent. In some embodiments, the control panel is displayed in responseto the input object meeting the second hover proximity criteria (e.g.,hover closer to the touch-sensitive surface). In some embodiments, whenthe input object meets the first hover proximity criteria while at afirst hover location, the device magnifies or highlights a portion ofthe user interface with activatable control(s) or link(s) that is belowthe input object. In some embodiments, the user can tap on or hovercloser to a particular activatable control or link in the magnifiedportion to activate it. Shifting content out of the way upon detectingthe input object hovering at a first hover distance and displaying auser interface object at the original location of the content when theinput object hovers closer to the touch-sensitive surface enhance theoperability of the device and make the user-device interface moreefficient (e.g., by providing a more responsive user interface, helpingthe user to achieve an intended result by providing the required inputs,and reduce user mistakes when operating/interacting with the device)which, additionally, reduce power usage and improve battery life of thedevice (e.g., by enabling the user to use the device more quickly andefficiently).

In some embodiments, displaying the first visual feedback that isassociated with the first hover proximity criteria includes (2022):applying a first change to an appearance of a first user interfaceobject that is already displayed on the display (e.g., highlighting afull-screen user interface that includes multiple sub-elements, orhighlighting or enlarging a container object that includes multiplesub-elements (e.g., a window, a toolbar, a dock, a list, a menu, a blockof content comprising sub-blocks of content) and that is alreadydisplayed in the user interface), wherein the first user interfaceobject includes a second user interface object (e.g., a first item,object, control, or sub-block of content) and a third user interfaceobject (e.g., a second item, object, control, or sub-block of content).Displaying the second visual feedback that is associated with the secondhover proximity criteria includes: applying a second change to anappearance of the second user interface object (e.g., highlighting orenlarging some of sub-elements of the first user interface object thatare displayed near the hover location of the input object) relative toan appearance of the third user interface object within the first userinterface object. Although the appearances of the second and thirdobjects may have been affected as a result of the first change that isapplied to the first user interface object as a whole when the inputobject met the first hover proximity criteria, the first change to theappearance of the first user interface object does not single out thesecond object relative to the third object. When the second hoverproximity criteria are met by the input object, the second change inappearance is selectively applied to the second user interface objectand not to the third user interface object or other user interfaceobjects in the first user interface objects based on the hover locationof the input object relative to the locations of the second and thirduser interface objects (e.g., when the hover location is closer to thesecond user interface object than the third user interface object, thesecond change in appearance is applied to the second user interfaceobject, instead of the third user interface object). As a more specificexample, in some embodiments, the first user interface object includes atool bar, and hovering over the tool bar at a first hover distancecauses the device to magnify the tool bar along with the controls withinthe tool bar, and while the tool bar remains magnified, hovering overthe tool bar at a second, closer hover distance causes the device tohighlight and/or magnify a first control within the tool bar that isclosest to the input object, while leaving the other controls unchanged.In another example, the first user interface includes several paragraphof text, and hovering over the first user interface at a first hoverdistance causes the device to select a first paragraph within the userinterface that is the closest to the hover location of the input object,and when the input object hovers over the user interface at a second,closer hover distance, the device ceases to select the first paragraph,and instead, selects a sentence within the first paragraph that isclosest to the current hover location of the input object. In someembodiments, when the input object meets the second hover proximitycriteria, the device deemphasizes other portions of the first userinterface object (e.g., blur or darken) relative to the second userinterface object that is closest to the hover location of the inputobject (and optionally keeping the second user interface objectunchanged). Highlighting a user interface object upon detecting theinput object hovering at a first hover distance and highlighting asub-element of the user interface object when the input object hoverscloser to the touch-sensitive surface enhance the operability of thedevice and make the user-device interface more efficient (e.g., byproviding a more responsive user interface, gradually guiding the user'sattention toward a small portion of the user interface, allowing theuser to adjust the input based on the visual feedback at the differentlevels, and reduce user mistakes when operating/interacting with thedevice) which, additionally, reduce power usage and improve battery lifeof the device (e.g., by enabling the user to use the device more quicklyand efficiently).

The first change to the appearance of the first user interface object ismaintained (2024) when the second change to the appearance of the seconduser interface object is applied. This is illustrated in FIGS. 10B-10Cand 10H-10I, for example. In some embodiments, when the input objecthovers over a tool bar at a first threshold hover distance, the tool baris magnified, and when the input object hovers closer over the tool barat a second threshold hover distance, a control in the tool bar that isclosest to the input object is highlighted while the tool bar remainsmagnified. When the input object is lifted away from the touch-sensitivesurface, the highlight of the control is canceled first, while themagnification of the tool bar is maintained until the input object ismore than the first threshold hover distance away from thetouch-sensitive surface. In some embodiments, when the input objectmoves laterally over the touch-sensitive surface from a location abovethe second user interface object to a location above the third userinterface object (while continuing to meet the second hover proximitythreshold), the highlight on the second user interface object iscanceled and the highlight is applied to the third user interfaceobject, while the tool bar continues to be magnified. Maintaining thevisual feedback previously shown when the input object hovers closer tothe touch-sensitive surface enhances the operability of the device andmakes the user-device interface more efficient (e.g., by graduallyguiding the user's attention toward a small portion of the userinterface while maintaining context for the new changes, helping theuser to achieve an intended result by providing the required inputs, andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device (e.g., by enabling the user to use the device more quicklyand efficiently).

In some embodiments, the first change to the appearance of the firstuser interface object is canceled (2026) when the second change to theappearance of the second user interface object is applied. This isillustrated in FIG. 10O-10P (notification list 1048 is replaced byexpanded notification list 1050) and FIGS. 10V-10W (cursor 1074 isreplaced by two selection handles 1084 and 1086), for example. In someembodiments, when the input object hovers over a paragraph of text at afirst threshold hover distance, the paragraph of text is selected, andwhen the input object hovers closer over the text at a second thresholdhover distance, the selection of the paragraph is canceled, and asentence within the paragraph becomes selected. In some embodiments,when the input object is lifted away from the touch-sensitive surface,the selection of the sentence is canceled. In some embodiments, theselection of the paragraph is restored. In some embodiments, theselection of the paragraph is not restored. In some embodiments, whenthe input object moves laterally over the touch-sensitive surface from alocation above a first sentence to a location above a second sentence(while continuing to meet the second hover proximity threshold), theselection of the first sentence is canceled and the second sentence isselected. Canceling the visual feedback previously shown when the inputobject hovers closer to the touch-sensitive surface enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by reducing visual clutter and avoiding user confusion,helping the user to achieve an intended result by providing the requiredinputs, and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device (e.g., by enabling the user to use the device morequickly and efficiently).

In some embodiments, displaying the first visual feedback that isassociated with the first hover proximity criteria includes (2028):applying a first change to an appearance of a first user interfaceobject that is already displayed on the display (e.g., highlighting orenlarging a user interface element (e.g., an application icon, a list, amenu, etc.) that is already displayed in the user interface). Displayingthe second visual feedback that is associated with the second hoverproximity criteria includes displaying a second user interface objectthat is associated with the first user interface object and that was notdisplayed with the first user interface object prior to the second hoverproximity criteria being met by the input object (e.g., the second userinterface object is a new object that is displayed in response to thesecond hover proximity criteria being met by the input object). As amore specific example, in some embodiments, the first user interfaceobject includes an application icon of a corresponding application, andhovering over the application icon at a first hover distance causes thedevice to select/highlight the application icon, and while theapplication icon remains selected/highlighted, hover over theapplication icon at a second, closer hover distance causes the device todisplay a tool-tip related to the application, an unread notificationfor the application, a quick action menu for the application, etc. Insome embodiments, tapping on the second user interface object while itis displayed causes an operation of the application to be performed(e.g., tool-tip turns into a help page, application launches to a userinterface corresponding to the communication that triggered thenotification, an action in the menu is performed, etc.). In someembodiments, the action is performed without launching the application.In another example, the first user interface object includes an item ina list (e.g., an email item in an inbox, or a message in a listing ofmessages, or a contact in a listing of contacts, or a conversation in alisting of conversations), and hovering over the list item at a firsthover distance causes the device to select/highlight the item, and whilethe item remains selected/highlighted, hover over the application iconat a second, closer hover distance causes the device to display apreview of the item (e.g., a pop-up platter with content correspondingto the item). In some embodiments, tapping on the second user interfaceobject while it is displayed causes the application to be launched to auser interface corresponding to the content of the preview. In anotherexample, the first user interface object includes a link to additionalcontent (e.g., a webpage), and hovering over the link at a first hoverdistance causes the device to select/highlight the link, and hoveringover the link at a second, closer hover distance causes the device todisplay a preview of the additional content (e.g., a pop-up platter withadditional content corresponding to the link). In some embodiments,tapping on the second user interface object while it is displayed causesthe content corresponding to the link to be fully displayed.Highlighting a user interface object upon detecting the input objecthovering at a first hover distance and creating a new user interfaceobject that is associated with the highlighted user interface objectwhen the input object hovers closer to the touch-sensitive surfaceenhance the operability of the device and make the user-device interfacemore efficient (e.g., by providing a more responsive user interface,gradually guiding the user's attention toward a new user interfaceobject in the user interface, providing more functions as needed withoutunnecessarily cluttering the user interface, and reduce user mistakeswhen operating/interacting with the device) which, additionally, reducepower usage and improve battery life of the device (e.g., by enablingthe user to use the device more quickly and efficiently).

In some embodiments, while displaying the second user interface object,the device detects (2030) that the second hover proximity criteria areno longer met: in accordance with a determination that the second hoverproximity criteria are no longer met because the input object has madecontact with the touch-sensitive surface, the device performs anoperation (e.g., opening a webpage, display full content of acommunication, launch an application, etc.) corresponding to the seconduser interface object (and ceasing to display the second user interfaceobject); and in accordance with a determination that the second hoverproximity criteria are no longer met and the first hover proximitycriteria are still met, the device ceases to display the second userinterface object (without performing an operation corresponding to thesecond user interface object). This is illustrated in FIG. 10F-10M, forexample. After the new user interface object (e.g., the second userinterface object) is displayed in response to the level-two hoverproximity criteria being met, the new user interface object is eitheractivated to perform an operation or ceases to be displayed depending onwhether the input object moves closer and makes contact with thetouch-sensitive surface or moves away and exits the level-two hoverproximity range. The two outcomes are both easily achievable by anatural progression of the current input. Therefore, the heuristic fordetermining whether to perform an operation or ceases to display the newuser interface object as described herein enhances the operability ofthe device and makes the user-device interface more efficient (e.g., byreducing the number of steps needed to perform a task, and providingadditional functional control options without cluttering the userinterface with additional displayed control).

in response to detecting that the second hover proximity criteria aremet by the input object, the device cancels (2032) the first change thathas been applied to the appearance of the first user interface object(e.g., ceasing to highlight or enlarge the first user interface object(e.g., the application icon, the list item, the link, etc.) that isalready displayed in the user interface. In response to detecting thatthe second hover proximity criteria are no longer met and the firsthover proximity criteria are still met (e.g., after canceling the firstchange that has been applied to the appearance of the first userinterface object), the device reapplies the first change to theappearance of the first user interface object that has been canceled. Insome embodiments, in response to detecting that both the first hoverproximity criteria and the second hover proximity criteria are no longermet because the input object has exited the hover proximity range abovethe touch-sensitive surface, the device cancels the first change thathas been reapplied to the appearance of the first user interface object.Ceasing to display the first visual feedback when the second hoverproximity criteria are met (e.g., during a hover-in process by the inputobject) helps to reduce visual clutter and avoid user confusion whenproviding inputs, and redisplaying the first visual feedback when thesecond hover proximity criteria are no longer met and the first hoverproximity criteria are still met (e.g., during the hover-out process bythe input object) helps to reduce the number of steps to redisplaypreviously displayed information, both of which enhance the operabilityof the device and make the user-device interface more efficient (e.g.,by reducing the number of steps needed to perform a task, helping theuser to achieve an intended result by providing the required inputs, andreducing user mistakes when operating/interacting with the device).

In some embodiments, displaying the first visual feedback that isassociated with the first hover proximity criteria includes (2034):displaying a first user interface object that was not displayed prior tothe first hover proximity criteria being met by the input object (e.g.,when the input object hovers over an application icon at a firstthreshold hover distance above the touch-sensitive surface, a quickaction menu associated with the application icon pops up from next tothe application icon). Displaying the second visual feedback that isassociated with the second hover proximity criteria includes: whilemaintaining display of the first user interface object, displaying asecond user interface object that is associated with the first userinterface object and that was not displayed with the first userinterface object prior to the second hover proximity criteria being metby the input object (e.g., the second user interface object is anothernew object that is displayed in response to the second hover proximitycriteria being met by the input object). In some embodiments, the seconduser interface object is displayed while the input object maintains itslateral position (no lateral movement) since the first user interfaceobject is displayed. In some embodiments, hovering over an applicationicon at a first hover distance causes the device to display a pop-upmenu associated with the application icon, and while the pop-up menu isdisplayed, hovering over the application icon (or the pop-up menu) at asecond, closer hover distance causes the device to display a sub-menu ofthe pop-up menu. In some embodiments, tapping on the sub-menu, or anitem in the sub-menu while it is displayed causes the device to performan operation of the application that corresponds to the sub-menu or menuitem. In some embodiments, the action is performed without launching theapplication. In some embodiments, after the sub-menu is displayed, whenthe input object moves away (with less than a threshold amount oflateral movement or no lateral movement) from the touch-sensitivesurface back to the first threshold hover distance above thetouch-sensitive surface, the device ceases to display the sub-menu,while continuing to display the menu. The device ceases to display themenu when the input object exits the first hover proximity range abovethe touch-sensitive surface. Displaying a first new user interfaceobject upon detecting the input object hovering at a first hoverdistance and creating a second new user interface object that isassociated with the first new object when the input object hovers closerto the touch-sensitive surface enhance the operability of the device andmake the user-device interface more efficient (e.g., by providing a moreresponsive user interface, gradually guiding the user's attention towarda new user interface object in the user interface, providing morefunctions as needed without unnecessarily cluttering the user interface,and reduce user mistakes when operating/interacting with the device)which, additionally, reduce power usage and improve battery life of thedevice (e.g., by enabling the user to use the device more quickly andefficiently).

In some embodiments, while displaying the second user interface object,detecting that the second hover proximity criteria are no longer met: inaccordance with a determination that the second hover proximity criteriaare no longer met because the input object has made contact with thetouch-sensitive surface, the device performs an operation correspondingto the second user interface object (e.g., activate an option in thesub-menu) (and ceasing to display the second user interface object); andin accordance with a determination that the second hover proximitycriteria are no longer met and the first hover proximity criteria arestill met, the device ceases to display the second user interface object(without performing an operation corresponding to the second userinterface object, and while maintaining display of the first userinterface object). After the second new user interface object isdisplayed in response to the level-two hover proximity criteria beingmet, the second new user interface object is either activated to performan operation or ceases to be displayed depending on whether the inputobject moves closer and makes contact with the touch-sensitive surfaceor moves away and exits the level-two hover proximity range. The twooutcomes are both easily achievable by a natural progression of thecurrent input. Therefore, the heuristic for determining whether toperform an operation or cease to display the second new user interfaceobject as described herein enhances the operability of the device andmakes the user-device interface more efficient (e.g., by reducing thenumber of steps needed to perform a task, and providing additionalfunctional control options without cluttering the user interface withadditional displayed controls).

In some embodiments, after detecting that the second hover proximitycriteria are no longer met, the device detects that the first hoverproximity criteria are no longer met. In response to detecting that thefirst hover proximity criteria are no longer met because the inputobject has exited the first hover proximity range above thetouch-sensitive surface, the device ceases to display the first userinterface object. Ceasing to display a currently displayed new objectwhen the input object is lifted out of the first-level hover proximityrange enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by reducing visual clutter and avoiduser confusion, helping the user to achieve an intended result byproviding the required inputs and reducing mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, displaying the first visual feedback that isassociated with the first hover proximity criteria includes (2040):displaying a first user interface object that was not displayed prior tothe first hover proximity criteria being met by the input object,wherein the first user interface object includes a plurality ofsub-elements, including a second user interface object and a third userinterface object (e.g., when the input object hovers over a media playerwindow or full screen media playing window at a first threshold hoverdistance above the touch-sensitive surface, a control panel associatedwith media player application is displayed over the media playerwindow). In some embodiments, the first user interface object isdisplayed at a location that corresponds to (e.g., directly below, orprojected from) the hover location of the input object at the time whenthe input object met the first hover proximity criteria. Displaying thesecond visual feedback that is associated with the second hoverproximity criteria includes: while maintaining display of the first userinterface object, applying a change to an appearance of the second userinterface object relative to an appearance of the third user interfaceobject. For example, in some embodiments, the second user interfaceobject is a pause button, and the third user interface object is a fastforward button. When the input object hovers closer to thetouch-sensitive surface at a second threshold hover distance, and theinput object is closer to the pause button than the fast forward button,the pause button is highlighted relative to the fast forward button (andother buttons in the control panel). In some embodiments, if the inputobject moves laterally and becomes closer to fast forward button thanthe pause button, the fast forward button is highlighted, and the pausebutton is no longer highlighted. In some embodiments, when the inputobject moves vertically and makes contact with the touch-sensitivesurface, the highlighted control (e.g., the fast forward button) isactivated and the media playing is fast forwarded. In some embodiments,when the input object hovers closer to the touch-sensitive surface at asecond threshold hover distance, and the input object is closer to thepause button than the fast forward button, the pause button isunchanged, while the fast forward button and other controls in thecontrol panel are deemphasized (e.g., darkened or blurred) relative tothe pause button. This is illustrated in FIGS. 10F-10M, for example.Displaying a new user interface object upon detecting the input objecthovering at a first hover distance and highlighting a sub-element withinthe new object when the input object hovers closer to thetouch-sensitive surface enhance the operability of the device and makethe user-device interface more efficient (e.g., by providing a moreresponsive user interface, gradually guiding the user's attention towarda portion of a new user interface object, providing more functions asneeded without unnecessarily cluttering the user interface, and reduceuser mistakes when operating/interacting with the device) which,additionally, reduce power usage and improve battery life of the device(e.g., by enabling the user to use the device more quickly andefficiently).

In some embodiments, while the first user interface object is displayed,the device detects (2042) a second movement (e.g., including a lateralmovement) of the input object from a third hover location to a fourthhover location while the input object continues to meet the first hoverproximity criteria. In response to detecting the second movement of theinput object while the input object continues to meet the first hoverproximity criteria, the device moves the first user interface objectfrom a first location on the display that corresponds to the third hoverlocation of the input object to a second location on the display that isdistinct from the first location on the display and that corresponds tothe fourth hover location of the input object. For example, in someembodiments, the playback control panel is displayed at a location thatcorresponds to the hover location of the input object at the time whenthe input object met the first hover proximity criteria, and theplayback control panel moves with the input object as the input objectmoves from a third hover location to a fourth hover location whileremaining within the first hover proximity range above thetouch-sensitive surface. This is illustrated in FIGS. 10G-10H, forexample. After a new user interface object is displayed upon detectingthe input object hovering at a first hover distance, moving the new userinterface object in accordance with a lateral hover movement within thefirst-level hover proximity range enhance the operability of the deviceand make the user-device interface more efficient (e.g., by allowing theuser to reposition the new user interface object to a more convenientlocation away from existing content on the user interface, therebyhelping the user to achieve an intended result by providing the requiredinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduce power usage and improve battery lifeof the device (e.g., by enabling the user to use the device more quicklyand efficiently).

In some embodiments, while the change to the appearance of the seconduser interface object is applied, the device detects (2044) that thesecond hover proximity criteria are no longer met. In response todetecting that the second hover proximity criteria are no longer met: inaccordance with a determination that the second hover proximity criteriaare no longer met because the input object has made contact with thetouch-sensitive surface, the device performs an operation correspondingto the second user interface object (e.g., activate the button that ishighlighted to control playback of media) (and optionally, maintainingdisplay of the first user interface object). In some embodiments, inaddition to requiring contact with the touch-sensitive surface, thedevice requires that a characteristic intensity of the contact increasesabove a first intensity threshold (e.g., a light press intensitythreshold) in order to trigger performance of the operation thatcorresponds to the second user interface object. In accordance with adetermination that the second hover proximity criteria are no longer metand the first hover proximity criteria are still met, the device cancelsthe change that has been applied to the appearance of the second userinterface object (without performing an operation corresponding to thesecond user interface object, and maintaining display of the first userinterface object). For example, when the input object moves away fromthe touch-sensitive surface and exits the second hover proximity range,the highlighting of a particular control nearest the input object iscanceled. After the new user interface object (e.g., the second userinterface object) is displayed and a sub-element within the new userinterface object is highlighted in response to the level-two hoverproximity criteria being met, the sub-element is either activated toperform an operation or ceases to be highlighted depending on whetherthe input object moves closer and makes contact with the touch-sensitivesurface or moves away and exits the level-two hover proximity range. Thetwo outcomes are both easily achievable by a natural progression of thecurrent input. Therefore, the heuristic for determining whether toperform an operation or ceases to highlight the sub-element within thenew user interface object as described herein enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by reducing the number of steps needed to perform a task, and providingadditional functional control options without cluttering the userinterface with additional displayed control).

In some embodiments, after detecting that the second hover proximitycriteria are no longer met, the device detects (2046) that the firsthover proximity criteria are no longer met. In response to detectingthat the first hover proximity criteria are no longer met because theinput object has exited the hover proximity range above thetouch-sensitive surface, the device ceases to display the first userinterface object (e.g., when the input object is lifted out of the firsthover proximity range, the device ceases to display the playback controlpanel on the media player user interface). Ceasing to display acurrently displayed new object when the input object is lifted out ofthe first-level hover proximity range enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byreducing visual clutter and avoid user confusion, helping the user toachieve an intended result by providing the required inputs and reducingmistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, displaying the first user interface object that wasnot displayed prior to the first hover proximity criteria being met bythe input object includes (2048): in accordance with a determinationthat the input object meets the first hover proximity criteria but notthe second hover proximity criteria, changing (e.g., increasing) anopacity of the first user interface object as the input object movescloser to the touch-sensitive surface. In some embodiments, the opacityof the first user interface object is reduced when the input objectmoves away from the touch-sensitive surface while still meeting thefirst hover proximity criteria. Changing an opacity of a newly displayedobject when the input object moves closer to the touch-sensitive surfaceenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by providing information about the stateof the input object, helping the user to achieve an intended result byproviding the required inputs, and reducing mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, displaying the first visual feedback that isassociated with the first hover proximity criteria includes (2050):applying a first change to an appearance of a first user interfaceobject that is already displayed in the first user interface. Displayingthe second visual feedback that is associated with the second hoverproximity criteria includes: while maintaining the first change to theappearance of the first user interface object, applying a second changeto the appearance of the first user interface object that is distinctand non-continuous from the first change that has been applied to thefirst user interface object. For example, in some embodiments, hoveringover selectable text to magnify the text (e.g., magnify a sentence thatis under the finger when the finger is at a first threshold hoverdistance above the touch-sensitive surface), and hovering closer toselect the magnified sentence (e.g., the magnified sentence is selectedwhen the finger moves to a second threshold hover distance above thetouch-sensitive surface). Upon detection of the finger moving laterallywhile meeting the first hover proximity criteria without meeting thesecond hover proximity criteria, the device displays different portionsof text that are magnified with the lateral movement of the finger; andupon detection of the finger moving laterally while meeting the secondhover proximity criteria, the device displays different portions of textare selected with the lateral movement of the finger. Applying twodifferent types of visual effect to an existing user interface objectdepending on whether the input object is detected in the level-one hoverproximity range or the level-two hover proximity range enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by indicating to the user the different states that thedevice is currently in, and thereby helping the user to achieve anintended result by providing the required inputs and reducing usermistakes when operating/interacting with the device) which,additionally, reduce power usage and improve battery life of the device(e.g., by enabling the user to use the device more quickly andefficiently).

In some embodiments, while displaying the second visual feedback, thedevice detects (2052) that third hover proximity criteria are met by theinput object, wherein the third hover proximity criteria require thatthe current value of the hover proximity parameter of the input objectis within a third value range, and wherein the third value range iswithin the second value range (e.g., the input object is less than 0.3cm away from the touch-sensitive surface without touching thetouch-sensitive surface) (in other words, the third hover proximitycriteria are more difficult to meet than second hover proximitycriteria, and when the third hover proximity criteria are met, the firstand second hover proximity criteria are also met, but not vice versa).In response to detecting that the third hover proximity criteria are metby the input object, the device displays a third visual feedback,distinct and non-continuous from the first and second visual feedback,that is associated with the third hover proximity range. Providingmultiple levels of distinct and non-continuous visual feedback inresponse to variations in a hover-proximity parameter (e.g., hoverdistance) of an input object enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to achieve an intended result by providing the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device (e.g., by enabling the user to use the device more quicklyand efficiently).

In some embodiments, displaying the first visual feedback that isassociated with the first hover proximity criteria includes (2054):applying a magnification to a first portion of selectable text that isdisplayed at a location that corresponds to a current hover location ofthe input object; and displaying a cursor that was not displayed beforethe first hover proximity criteria were met by the input object (e.g.,displaying the cursor within the portion of the selectable text that hasbeen magnified). Displaying the second visual feedback that isassociated with the second hover proximity criteria includes: while themagnification is applied to the first portion of the selectable text andthe cursor is displayed, changing an appearance of the cursor toindicate that text selection mode is activated (e.g., includingenhancing the color and thickness of the cursor or adding a lollipop ontop of the cursor, or next to the cursor). This is illustrated in FIGS.10T-10Y, for example. In some embodiments, in addition to requiring thefirst hover proximity criteria to be met by the input object, the devicefurther requires that the input object is held with less than athreshold amount of movement for a threshold amount of time within thefirst hover proximity range in order to apply the magnification anddisplay the cursor. In some embodiments, in addition to requiring thefirst hover proximity criteria to be met by the input object, the devicefurther requires that the input object makes contact with thetouch-sensitive surface first before hovering and holding the inputobject within the first hover proximity range, in order to apply themagnification and display the cursor. In some embodiments, in additionto requiring the first hover proximity criteria to be met by the inputobject, the device further requires that the input object makes contactwith the touch-sensitive surface and presses against the touch-sensitivesurface with more than a threshold intensity before hovering and holdingthe input object within the first hover proximity range, in order toapply the magnification and display the cursor. Highlighting selectabletext and displaying a cursor upon detecting the input object hovering ata first hover distance and changing the appearance of the cursor toindicate that text selection mode is activated when the input objecthovers closer to the touch-sensitive surface enhance the operability ofthe device and make the user-device interface more efficient (e.g., byproviding a more responsive user interface, providing additionalfunctions as needed without unnecessarily cluttering the user interfacewith additional displayed controls, and reducing user mistakes whenoperating/interacting with the device) which, additionally, reduce powerusage and improve battery life of the device (e.g., by enabling the userto use the device more quickly and efficiently).

In some embodiments, the device detects (2056) lateral movement of theinput object. In response to detecting the lateral movement of the inputobject: in accordance with a determination that the second hoverproximity criteria are met by the input object during the lateralmovement of the input object: the device moves the cursor in accordancewith the lateral movement of the input object (e.g., moving the cursorwith a user interface object that represents a boundary of the selectionin accordance with the lateral movement of the input object); and thedevice selects text in accordance with the movement of the cursor (e.g.,selecting text in accordance with the movement of the cursor with thelollipop on top). In accordance with a determination that the firsthover proximity criteria are met by the input object and the secondhover proximity criteria are not met during the lateral movement of theinput object: the device moves the cursor in accordance with the lateralmovement of the input object (e.g., moving the cursor without moving theuser interface object that represents the boundary of the selection inaccordance with the lateral movement of the input object) withoutselecting text. This is illustrated in FIGS. 10T-10Y, for example.Performing different functions in response to lateral hover movement(e.g., moving the cursor or resizing text selection) depending onwhether the lateral hover movement occurs within the second-level hoverproximity range or outside of the second-level hover proximity rangeenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by providing additional functionswithout cluttering the user interface with additional displayedcontrols, reducing the number of inputs needed to perform a desiredoperation, helping the user to achieve an intended result by providingthe required inputs, and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device (e.g., by enablingthe user to use the device more quickly and efficiently).

In some embodiments, in response to detecting the lateral movement ofthe input object: in accordance with a determination that the inputobject is in contact with the touch-sensitive surface during the lateralmovement of the input object: the device scrolls (2058) the userinterface in accordance with the lateral movement of the input object(e.g., without moving the cursor, without selecting text). Performingdifferent functions in response to lateral movement (e.g., moving thecursor, resizing text selection, or scrolling the user interface)depending on whether the lateral movement occurs during hover or whilemaintaining contact with the touch-sensitive surface enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by providing additional functions without clutteringthe user interface with additional displayed controls, reducing thenumber of inputs needed to perform a desired operation, helping the userto achieve an intended result by providing the required inputs, andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device (e.g., by enabling the user to use the device more quicklyand efficiently).

It should be understood that the particular order in which theoperations in FIGS. 20A-20I have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 1500, 1600, 1700, 1800, 1900, 2100, 2200, 2300, and 2400) arealso applicable in an analogous manner to method 2000 described abovewith respect to FIGS. 20A-20I. For example, the contacts, gestures,input objects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described above with reference to method 2000 optionally haveone or more of the characteristics of the contacts, gestures, inputobjects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described herein with reference to other methods describedherein (e.g., methods 1500, 1600, 1700, 1800, 1900, 2100, 2200, 2300,and 2400). For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 20A-20I are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, detection operations 2004 and 2008 are, optionally, implementedby event sorter 170, event recognizer 180, and event handler 190. Eventmonitor 171 in event sorter 170 detects a contact on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether a first contact at a firstlocation on the touch-sensitive surface corresponds to a predefinedevent or sub-event, such as selection of an object on a user interface.When a respective predefined event or sub-event is detected, eventrecognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

FIGS. 21A-21D are flow diagrams illustrating a method 2100 ofinteracting with a user interface object through proximity-based andcontact-based inputs in accordance with some embodiments. The method2100 is performed at an electronic device (e.g., device 300, FIG. 3, orportable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the electronic deviceincludes one or more first sensors to detect proximity of an inputobject (e.g., a finger or a stylus) above the touch-sensitive surface(e.g., proximity sensors (such as infrared sensors), capacitive sensorsin the touch sensitive surface, or cameras next to the touch-sensitivesurface) and one or more second sensors to detect intensities of contactof the input object with the touch-sensitive surface. In someembodiments, the one or more second sensors are different from the oneor more first sensors. In some embodiments, the one or more secondsensors are the same as the one or more first sensors. In someembodiments, the touch-sensitive surface and the display are integratedinto a touch-sensitive display. In some embodiments, the display is atouch-screen display and the touch-sensitive surface is on or integratedwith the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 2100 are, optionally,combined and/or the order of some operations is, optionally, changed.

Method 2100 relates to conditionally performing an operation inaccordance with a hover-move input by an input object when the inputobject has met both the usual hover proximity criteria for detecting ahover input and an additional requirement that augments the usual hoverproximity criteria (e.g., a time threshold for holding the input objectin place, or a closer hover proximity range, etc.) before the movementof the input object. The additional requirement that augments the usualhover proximity criteria serves as a trigger for entering a mode inwhich the operation is performed; and once the mode is entered, theinput object no longer needs to meet the additional requirement tocontinue the operation or to repeat performance of the operation (e.g.,with respect to another object), as long as the input object continuesto meet the usual hover proximity criteria. By using an augmentedrequirement that can be satisfied by a single input, rather than acombination of multiple inputs (e.g., multiple concurrent or sequentialinputs), as the condition for entering a particular operation mode, thedevice reduces the number of inputs needed to perform an operation andthereby enhancing the operability of the device and making theuser-device interface more efficient. Additionally, by not requiring theinput object to continue to meet the augmented requirement during thehover-move input, the device also makes it easier for the user tocontinue or repeat performance of the operation, thereby enhancing theoperability of the user device and making the user-device interface moreefficient (e.g., by reducing user mistakes when operating/interactingwith the device).

The device displays (2102), in a first user interface, a plurality ofuser interface objects that includes at least a first user interfaceobject. While displaying the plurality of user interface objects, thedevice detects (2104) an input object at a first hover location over thefirst user interface object that meets first hover proximity criteria(e.g., a hover proximity parameter of the input object within a firsthover proximity range above the touch-sensitive surface). Afterdetecting the input object at the first hover location over the firstuser interface object that meets the first hover proximity criteria, thedevice detects (2106) movement of the input object away from the firsthover location (e.g., detecting a change in the hover location of theinput object, including a change in the lateral position of the inputobject, and a change in the vertical position of the input object). Inresponse to detecting movement of the input object away from the firsthover location: in accordance with a determination that the input objectmeets first augmented hover proximity criteria, wherein the firstaugmented hover proximity criteria require that the input object had metthe first hover proximity criteria and an additional requirement thataugments the first hover proximity criteria before the input objectmoved away from the first location (e.g., the additional requirement isthat the input object meets the first hover proximity criteria with lessthan a predetermined amount of movement for more than a threshold amountof time (e.g., the input object was held substantially stationary for athreshold amount of time while meeting the first hover proximitycriteria)), the device performs (2108) a first operation associated withthe movement of the input object (e.g., selecting an edge of a textselection box and move it relative to another edge of the text selectionbox, or ceasing to display a tool-tip associated with the first userinterface object and displaying a tool tip for a second user interfaceobject that is distinct from the first user interface object when theinput object moves to a second hover location above the second userinterface object); and in accordance with a determination that the inputobject does not meet the first augmented hover proximity criteria (e.g.,because the input object had not met the additional requirement withless than the predetermined amount of movement before the input objectmoved away from the first hover location) (e.g., because the inputobject had not met either the first hover proximity criteria or theadditional requirement (e.g., the input object has been lifted out ofthe hover proximity range above the touch-sensitive surface)), thedevice forgoes performing the first operation. This is illustrated inFIGS. 11A-11G, where finger 734 is hovered over application icon 1104for a threshold amount of time to trigger notification redisplay mode,and when finger 734 moves over to another icon 1106, notification 1112for icon 1106 is redisplayed without requiring finger 734 to be hoveredover for that threshold amount of time.

In some embodiments, the first augmented hover proximity criteriarequire (2110) that the input object had continued to meet the firsthover proximity criteria for more than a predetermined amount of timewith less than the predetermined amount of movement before the inputobject moved away from the first hover location. This is illustrated inthe example shown in FIGS. 11A-11G, for example. Conditionallyperforming an operation in accordance with a hover-move input by aninput object when the input object had met a hover-hold requirementbefore the input object moved away reduces the number of inputs neededto perform the operation and thereby enhancing the operability of thedevice and making the user-device interface more efficient.Additionally, by not requiring the input object to continue to meet thehover-hold criteria during the hover-move input, the device also makesit easier for the user to continue or repeat performance of theoperation, thereby enhancing the operability of the user device andmaking the user-device interface more efficient (e.g., by reducing usermistakes when operating/interacting with the device).

In some embodiments, the first augmented hover proximity criteriarequire (2112) that the input object meets second hover proximitycriteria (for more than a predetermined amount of time with less thanthe predetermined amount of movement) before the input object moved awayfrom the first hover location, wherein the first hover proximitycriteria require that a current hover proximity parameter of the inputobject is within a first value range, the second hover proximitycriteria require that the current hover proximity parameter of the inputobject is within a second value range, and the second value range iswithin the first value range (e.g., the second hover proximity criteriarequire that the input object to be held closer to the touch-sensitivesurface than the first hover proximity criteria). Conditionallyperforming an operation in accordance with a hover-move input by aninput object when the input object had met a close-hover requirementbefore the input object moved away reduces the number of inputs neededto perform the operation, and thereby enhancing the operability of thedevice and making the user-device interface more efficient.Additionally, by not requiring the input object to continue to meet theclose-hover requirement during the hover-move input, the device alsomakes it easier for the user to continue or repeat performance of theoperation, thereby enhancing the operability of the user device andmaking the user-device interface more efficient (e.g., by reducing usermistakes when operating/interacting with the device). It is noted that,descriptions of embodiments that require a hover-hold input for acertain response may require the input object to hover closer (e.g.,meeting a smaller hover proximity range without meeting the timethreshold of the “hold” requirement) to achieve the same response.Similarly, descriptions of embodiments that require the input object tocome within a closer hover distance (e.g., level-two hover proximityrange) for a certain response may require the input object to hover andhold for a threshold amount of time to achieve the same response.Therefore, the examples shown in FIGS. 10A-10Y are applicable to method1100 as well. In the interest of brevity, different permutations ofcriteria and response are not enumerated here.

In some embodiments, performing the first operation includes (2114)changing an appearance of the first user interface object (e.g.,displaying a shadow behind the first user interface object, highlightingthe first user interface object, adding a lollipop on top of the objectwhen the object is a cursor, lifting the object off of its originalz-plane, changing the color of the object when the object is a lollipop,etc.) to indicate that a mode associated performing the first operationhas been entered (e.g., tool-tip display mode for displaying tool-tipsassociated with icons or controls, notification display mode fordisplaying unread notifications from applications corresponding toapplication launch icons, preview-display mode for displaying previewsof list items, text selection mode for moving a selection handle orlollipop to change a size of a selection, etc.)). Providing a visualindication that a mode associated with performing the first operationhas been entered by changing the appearance of the first user interfaceobject enhances the operability of the device and making the user-deviceinterface more efficient (e.g., by alerting the user of the change inthe state of the device and helping the user to achieve an intendedresult by providing the required inputs), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, performing the first operation includes (2116)changing a size of a selection in accordance with the movement of theinput object (e.g., changing a size or boundary of a text selection inaccordance with the movement of the input object after the input objecthas hovered over the selectable text for more than a threshold amount oftime). In some embodiments, the first user interface object is an edgeof a selection box or a selection handle on a selection box, or acursor. In some embodiments, if the input object is not held over thefirst user interface object for more than the threshold amount of time,the movement of the input object moves the first user interface objectwithout selecting text or expanding selected text). In some embodiments,the first user interface object is a cursor, and when the firstaugmented hover proximity criteria are met by the input object, theappearance of the cursor changes (e.g., a selection handle is displayedor existing selection handle is enlarged or changes color) to indicatethat the text selection mode is entered, and subsequent movement of thecursor with the changed appearance in accordance with the movement ofthe input object changes the size of a selection (e.g., expands textselection). In some embodiments, touch-down of the input object on thetouch-sensitive surface confirms the selection (e.g., selection remainsafter the input object is then lifted out of the hover proximity rangeabove the touch-sensitive surface). In some embodiments, lifting theinput object out of the hover proximity range without first touchingdown on the touch-sensitive surface cancels the text selection.Conditionally changing a size of a selection in accordance with ahover-move input by an input object when the input object has met boththe usual hover proximity criteria for detecting a hover input and anadditional requirement that augments the usual hover proximity criteria(e.g., a time threshold for holding the input object in place, or acloser hover proximity range, etc.) before the movement of the inputobject enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by reducing the number of inputs neededto change the size of a selection and reducing user mistakes whenoperating/interacting with the device).

In response to detecting movement of the input object away from thefirst hover location: in accordance with the determination that theinput object does not meet the first augmented hover proximity criteria,the device moves (2118) the first user interface object in accordancewith the movement of the input object, without changing the size of theselection (e.g., in some embodiments, when the first augmented hoverproximity criteria are not met by the input object, the appearance ofthe cursor does not change and the selection mode is not entered; andthe movement of the input object repositions the cursor in theselectable text without selecting text)). In some embodiments,touch-down of the input object on the touch-sensitive surface confirmsthe movement of the cursor (e.g., cursor remains at the new locationafter the input object is then lifted out of the hover proximity rangeabove the touch-sensitive surface). In some embodiments, lifting theinput object out of the hover proximity range without first touchingdown on the touch-sensitive surface cancels the move and restores thecursor back to its original location before the move. In someembodiments, a quick flick without touch-down throws the first userinterface object laterally across the first user interface and the firstuser interface settles into a final location (e.g., a snap location).Conditionally move a cursor (as opposed to change the size of aselection) in accordance with a hover-move input by an input object whenthe input object has not met both the usual hover proximity criteria fordetecting a hover input and an additional requirement that augments theusual hover proximity criteria before the movement of the input objectenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by reducing the number of inputs neededto move the cursor and reducing user mistakes when operating/interactingwith the device).

In some embodiments, detecting movement of the input object away fromthe first hover location includes (2120) detecting movement of the inputobject to a second hover location over a second user interface object ofthe plurality of user interface objects (e.g., now the second userinterface object has input focus). Performing the first operationincludes displaying second information about the second user interfaceobject in response to detecting the input object at the second hoverlocation over the second user interface object (e.g., when the inputobject moves to over the second user interface object, the devicedisplays a tooltip or preview corresponding to the second user interfaceobject, as long as the augmented hover proximity criteria had been metby the input object before the input object moved to the second hoverlocation, and the input object continues to meet the first hoverproximity criteria while the input object is detected at the secondhover location). Conditionally displaying information (e.g., a secondtool tip or pop-up window associated with a second object) in accordancewith a hover-move input by an input object when the input object has metboth the usual hover proximity criteria for detecting a hover input andan additional requirement that augments the usual hover proximitycriteria before the movement of the input object enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by reducing the number of inputs needed to display theinformation associated with the second object and reducing user mistakeswhen operating/interacting with the device).

In some embodiments, the device detects (2122) that the input objectmeets the first hover proximity criteria and the additional requirementthat augment the first hover proximity criteria before the input objectmoved away from the first location. In response to detecting that theinput object meets the first hover proximity criteria and the additionalrequirement that augment the first hover proximity criteria before theinput object moved away from the first hover location, the devicedisplays first information about the first user interface object (e.g.,when the input object hover over the first user interface object andholds for more than the threshold amount of time, the device displays aninformation pop-up, a menu, or a preview that corresponds to the firstuser interface object; or when the input object is brought within athreshold distance to the touch-sensitive surface that is closer thanthe regular hover proximity range, the device displays an informationpop-up, a menu, or a preview that corresponds to the first userinterface object). Prior to conditionally displaying second informationabout a second object, displaying first information about a first objectwhen the augmented hover proximity criteria are met before the movementof the input object enhances the operability of the device and makes theuser-device interface more efficient (e.g., by reducing the number ofinputs needed to display information about the first object and reducinguser mistakes when operating/interacting with the device).

In some embodiments, performing the first operation includes (2124)ceasing to display first information about the first user interfaceobject (e.g., ceasing to display a tool-tip or preview corresponding tothe first user interface object (e.g., a first application launch iconor a first list item) that has been displayed in response to the inputobject meeting the first augmented hover proximity criteria (e.g., hoverand hold still for a threshold amount of time over the first userinterface object, or hover sufficiently close to the first userinterface object)). Ceasing to display the first information when theinput object moves away from the first object when the augmented hoverproximity criteria have been met before the movement of the input objectenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended result by providing the required inputs and reducing usermistakes when operating/interacting with the device).

In some embodiments, displaying the second information about the seconduser interface object includes (2126) displaying the second informationwithout requiring that the input object meets the first augmented hoverproximity criteria (e.g., without requiring that the input object meetsboth the first hover proximity criteria and the additional requirementthat augment the first hover proximity criteria at the second hoverlocation). By not requiring the input object to continue to meet theaugmented requirement during the hover-move input, the device also makesit easier for the user to display the information about an additionalobject (e.g., the second object), thereby enhancing the operability ofthe user device and making the user-device interface more efficient(e.g., by reducing user mistakes when operating/interacting with thedevice).

In some embodiments, after displaying the second information about thesecond user interface object in response to detecting the input objectat the second hover location over the second user interface object, thedevice detects (2128) that the input object no longer meets the firsthover proximity criteria because the input object has exited a hoverproximity range above the touch-sensitive surface. In response todetecting that the input object no longer meets the first hoverproximity criteria because the input object has exited the hoverproximity range above the touch-sensitive surface, the device ceases todisplay the second information about the second user interface object(and ceasing to display the first information about the first userinterface object if the first information has been maintained after themovement of the input object from the first location to the secondlocation). Ceasing to display the information about an object when theinput object exits the hover proximity range enhances the operability ofthe user device and makes the user-device interface more efficient(e.g., by providing timely feedback regarding the state of the device,helping the user to achieve an intended result by providing the requiredinputs, and reducing user mistakes when operating/interacting with thedevice).

In some embodiments, after detecting that the input object no longermeets the first hover proximity criteria because the input object hasexited the hover proximity range above the touch-sensitive surface, thedevice detects (2130) that the input object meets the first hoverproximity criteria again after the input object has reentered the hoverproximity range at the second location above the second user interfaceobject. In response to detecting that the input object meets the firsthover proximity criteria at the second location above the second userinterface object: in accordance with a determination that the inputobject meets the first augmented hover proximity criteria, the deviceredisplays the second information about the second user interfaceobject; and in accordance with a determination that the input objectdoes not meet the first augmented hover proximity criteria, the deviceforgoes redisplaying the second information about the second userinterface object. This is illustrated in FIGS. 11I-11J, for example.After the device has exited the mode for displaying the information,requiring the input object to meet the augmented requirement again toredisplay the information about the second object enhances theoperability of the user device and makes the user-device interface moreefficient (e.g., by avoiding accidentally triggering display of theinformation and reducing user mistakes when operating/interacting withthe device).

In some embodiments, the first user interface object and the second userinterface objects are (2132) of a first type of objects, and the firstinformation and the second information are of a first type ofinformation. For example, the plurality of user interface objects areapplication launch icons on a home screen, or list items in a list. Insome embodiments, the first information and the second information aretool-tips or previews that are displayed in proximity to theircorresponding application launch icons or list items. In someembodiments, the first information and the second information aretool-tips or notifications that are displayed at a designated locationon the display (e.g., in a banner area at the top portion of thedisplay), independent of the respective locations of their correspondingapplication launch icons or list items. In some embodiments, the firstinformation ceases to be displayed when the second information isdisplayed. In some embodiments, the first information ceases to bedisplayed when the input object moves away from the first location overthe first user interface object. In some embodiments, the firstinformation ceases to be displayed when the input object exits the hoverproximity range, e.g., by touch-down on the touch-sensitive surface, orby moving up and exiting the hover proximity range above thetouch-sensitive surface. Having the mode for displaying informationabout object to only display the same type of information for the sametype of objects enhances the operability of the user device and makesthe user-device interface more efficient (e.g., by conforming to user'sexpectations and reducing user mistakes when operating/interacting withthe device), which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

It should be understood that the particular order in which theoperations in FIGS. 21A-21D have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 1500, 1600, 1700, 1800, 1900, 2000, 2200, 2300 and 2400) arealso applicable in an analogous manner to method 2100 described abovewith respect to FIGS. 21A-21D. For example, the contacts, gestures,input objects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described above with reference to method 2100 optionally haveone or more of the characteristics of the contacts, gestures, inputobjects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described herein with reference to other methods describedherein (e.g., methods 1500, 1600, 1700, 1800, 1900, 2000, 2200, 2300 and2400). For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 21A-21D are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, detection operations 2104 and 2106, and performing operation2108 are, optionally, implemented by event sorter 170, event recognizer180, and event handler 190. Event monitor 171 in event sorter 170detects a contact on touch-sensitive display 112, and event dispatchermodule 174 delivers the event information to application 136-1. Arespective event recognizer 180 of application 136-1 compares the eventinformation to respective event definitions 186, and determines whethera first contact at a first location on the touch-sensitive surfacecorresponds to a predefined event or sub-event, such as selection of anobject on a user interface. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally utilizes or calls data updater 176 or objectupdater 177 to update the application internal state 192. In someembodiments, event handler 190 accesses a respective GUI updater 178 toupdate what is displayed by the application. Similarly, it would beclear to a person having ordinary skill in the art how other processescan be implemented based on the components depicted in FIGS. 1A-1B.

FIGS. 22A-22G are flow diagrams illustrating a method 2200 ofinteracting with a user interface object through proximity-based andcontact-based inputs in accordance with some embodiments. The method2200 is performed at an electronic device (e.g., device 300, FIG. 3, orportable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the electronic deviceincludes one or more first sensors to detect proximity of an inputobject (e.g., a finger or a stylus) above the touch-sensitive surface(e.g., proximity sensors (such as infrared sensors), capacitive sensorsin the touch sensitive surface, or cameras next to the touch-sensitivesurface) and one or more second sensors to detect intensities of contactof the input object with the touch-sensitive surface. In someembodiments, the one or more second sensors are different from the oneor more first sensors. In some embodiments, the one or more secondsensors are the same as the one or more first sensors. In someembodiments, the touch-sensitive surface and the display are integratedinto a touch-sensitive display. In some embodiments, the display is atouch-screen display and the touch-sensitive surface is on or integratedwith the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 2200 are, optionally,combined and/or the order of some operations is, optionally, changed.

Method 2200 relates to providing visual feedback to indicate whether auser interface object has differentiated, object-specific responses tointensity-based touch inputs (e.g., activating a default function inresponse to a light tap vs. displaying a menu in response to a deeppress) before any intensity-based input is detected in relation to theuser interface object. Specifically, the device provides the visualindication for such “intensity-reactive” user interface objects when aninput object is detected near one of such user interface objects withina hover-proximity range above the touch-sensitive surface. Providing avisual indication to the user regarding whether a user interface objectis “intensity-reactive” while the input object is hovering over the userinterface object allows the user to receive information without makingcontact with the touch-sensitive surface or supplying the necessaryforce to accidentally activating a function that corresponds to the userinterface object. Providing such improved visual feedback to indicatethe intensity-reaction behavior of a user in response to a hover inputenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended result by providing the required inputs and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

The device displays (2202) a plurality of user interface objects (e.g.,application launch icons for launching respective applications),including a first user interface object, on the display. The devicedetects (2204) a first portion of an input by an input object, includingdetecting the input object at a first hover location above thetouch-sensitive surface while the input object meets first hoverproximity criteria (e.g., the first hover proximity criteria requirethat a hover proximity parameter of the input object is within a firstrange (e.g., the input object is within a first hover distance above thetouch-sensitive surface)), wherein the first hover location above thetouch-sensitive surface corresponds to a location of the first userinterface object on the display (e.g., the first hover location isdirectly above or is within a three-dimensional reactive region of thedisplay location of the first user interface object). In response todetecting the first portion of the input, including detecting the inputobject at the first hover location above the touch-sensitive surfacewhile the input object meets the first hover proximity criteria: inaccordance with a determination that the first user interface object hasdifferentiated responses to intensity-based inputs (e.g., in accordancewith a determination that the first user interface object has a firstobject-specific response (e.g., displaying a preview or menu) to a firstinput by a contact with a first characteristic intensity (e.g., a pressinput) and has a second object-specific response (e.g., launch anapplication or open a document) to a second input by the contact with asecond characteristic intensity (e.g., a tap input), and so on), thedevice displays (2206) first visual feedback in association with thefirst user interface object (e.g., displaying a shadow or an edge of apreview platter behind the first user interface object, or blurring therest of the user interface around the first user interface object, orshowing the first user interface object floating up from the originalz-plane of the first user interface object toward the user, orhighlighting or shining a spot light on the first user interface object,and/or otherwise altering an appearance of the first user interfaceobject) to indicate that the first user interface object hasdifferentiated responses to intensity-based inputs; and, in accordancewith a determination that the first user interface object does not havedifferentiated responses to intensity-based inputs (e.g., in accordancewith a determination that the first user interface object has a uniformresponse to input by a contact irrespective of a characteristicintensity of the contact), the device foregoes displaying the firstvisual feedback in association with the first user interface object. Insome embodiments, the device implements a failure feedback for thoseuser interface objects that do not have differentiated object-specificresponses to intensity-based inputs, such as displaying anon-object-specific canned animation and/or providing a non-objectspecific haptic feedback that indicates a lack of object-specificresponse for a press input that meets a certain intensity threshold.Even though this failure feedback is different from the normalobject-specific responses for a tap input on the user interface objects,these user interface objects are nonetheless considered to not havedifferentiated responses to intensity-based inputs for the purposes ofdisplaying the first visual feedback. This is illustrated in FIGS.12A-12E, for example.

In some embodiments, displaying the first visual feedback includes(2208) dynamically varying a visual effect that is displayed inaccordance with a current hover proximity parameter of the input objectwhile the input object is within a first threshold range from the firstuser interface object (e.g., varying a size or appearance of the shadowor the edge of a preview platter behind the first user interface object,or varying an amount of blurring that is applied to the rest of the userinterface around the first user interface object, or varying thez-height of the first user interface object above the original z-planeof the first user interface object, or varying the brightness of thehighlighting or the spot light shone on the first user interface object,and/or otherwise varying the amount of changes that is applied to theappearance of the first user interface object, in accordance with thecurrent hover distance of the input object above the touch-screen whilethe input object is within the three dimensional reactive region of thefirst user interface object). This is illustrated in FIGS. 12B-12, forexample. Dynamically varying a visual effect in accordance with acurrent hover proximity parameter of the input object while the inputobject is hovering over the user interface object allows the user toreceive information about how close the input object is to thetouch-sensitive surface enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toachieve an intended result by providing the required inputs and reducinguser mistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, in response to detecting the first portion of theinput, including detecting the input object at the first hover locationabove the touch-sensitive surface while the input object meets the firsthover proximity criteria: in accordance with the determination that thefirst user interface object does not have differentiated responses tointensity-based inputs, the device displays (2210) second visualfeedback (e.g., showing a different type of feedback or just thebeginning portion of the first visual feedback to indicate to the userthat the hover proximity criteria are met (e.g., displaying a shadow fora very brief period)) that is distinct from the first visual feedback inassociation with the first user interface object to indicate that thefirst user interface object does not have differentiated responses tointensity-based inputs. This is illustrated in FIG. 12D-12E, forexample. Showing a different visual effect for a non-intensity-reactiveobject helps to distinguish an intensity-reactive object and annon-intensity-reactive object before the input object makes contact withthe touch-sensitive surface enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to achieve an intended result by providing the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, displaying the second visual feedback includes(2212) displaying a visual effect that is independent of variation ofthe current hover proximity parameter of the input object while theinput object is within a first threshold range from the first userinterface object (e.g., displaying a static visual effect, or a cannedanimation (e.g., a canned animation that shows an initial portion of thevisual effect that is displayed for an object that has differentiatedresponses to intensity-based inputs and then cuts out) while the inputobject is within the three-dimensional reactive region of the first userinterface object). This is illustrated in FIGS. 12D-12E, for example.Showing a different visual effect that does not vary in accordance witha current hover proximity parameter of the input object helps todistinguish an intensity-reactive object and an non-intensity-reactiveobject before the input object makes contact with the touch-sensitivesurface enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended result by providing the required inputs and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the device detects (2214) a second portion of theinput by the input object, including detecting movement of the inputobject from the first hover location to a second hover location, whereinthe second hover location corresponds to a second user interface objectthat is distinct from the first user interface object (e.g., the secondhover location is directly above or is within a three-dimensionalreactive region of the display location of the second user interfaceobject), and wherein the second user interface object has differentiatedresponses to intensity-based inputs. In response to detecting the secondportion of the input, including detecting the movement of the inputobject from the first hover location to the second hover location: inaccordance with a determination that the input object meets second hoverproximity criteria (e.g., in some embodiments, the second hoverproximity criteria is the same as the first hover proximity criteria; insome embodiments, the second hover proximity criteria are less stringentrequirements than the first hover proximity criteria and are metwhenever the first hover proximity criteria are met), the devicedisplays the first visual feedback in association with the second userinterface object (e.g., displaying a shadow or an edge of a previewplatter behind the second user interface object, or blurring the rest ofthe user interface around the second user interface object, and/orhighlighting or shining a spot light on the second user interfaceobject) to indicate that the second user interface object hasdifferentiated responses to intensity-based inputs. This is illustratedin FIG. 12F, for example. In some embodiments, in response to detectingthe movement of the input object from the first hover location to thesecond hover location, the device, in accordance with a determinationthat the input object does not meet the second hover proximity criteria,forgoes display of the first visual feedback in association with thesecond user interface object. Showing the same visual effect forintensity-reactive objects when the input object hovers over theintensity-reactive objects helps to call out these intensity-reactiveobjects from other objects in the user interface, thereby enhancing theoperability of the device and making the user-device interface moreefficient (e.g., by helping the user to achieve an intended result byproviding the required inputs and reducing user mistakes whenoperating/interacting with the device).

In some embodiments, the device detects (2216) a third portion of theinput by the input object, including detecting movement of the inputobject from the second hover location to a third hover location, whereinthe third hover location corresponds to a third user interface objectthat is distinct from the first user interface object and the seconduser interface object (e.g., the third hover location is directly aboveor is within a three-dimensional reactive region of the display locationof the third user interface object), and wherein the third userinterface object does not have differentiated responses tointensity-based inputs. In response to detecting the third portion ofthe input, including detecting the movement of the input object from thesecond hover location to the third hover location: in accordance with adetermination that the input object meets the second hover proximitycriteria, the device displays the second visual feedback in associationwith the third user interface object (e.g., displaying a static visualeffect, or a canned animation (e.g., a canned animation that shows aninitial portion of the visual effect that is displayed for an objectthat has differentiated responses to intensity-based inputs and thencuts out) while the input object is within the three-dimensionalreactive region of the third user interface object) to indicate that thethird user interface object does not have differentiated responses tointensity-based inputs. This is illustrated in FIG. 12G, for example.Showing the same visual effect for non-intensity-reactive objects whenthe input object hovers over the intensity-reactive objects helps tocall out these non-intensity-reactive objects from other objects in theuser interface, thereby enhancing the operability of the device andmaking the user-device interface more efficient (e.g., by helping theuser to achieve an intended result by providing the required inputs andreducing user mistakes when operating/interacting with the device).

In some embodiments, the device detects (2218) a continuation of thefirst portion of the input by the input object, including detecting adecrease in a hover proximity parameter of the input object over thelocation on the touch-sensitive surface that corresponds to the firstuser interface object until the input object makes contact with thetouch-sensitive surface at a first contact location that corresponds tothe first user interface object. While the input object maintainscontact with the touch-sensitive surface, the device detects an increasein a characteristic intensity of a contact by the input object with thetouch-sensitive surface above a first intensity threshold (e.g., a lightpress intensity threshold). In response to detecting the increase in thecharacteristic intensity of the contact above the first intensitythreshold: in accordance with a determination that the first userinterface object has differentiated responses to intensity-based inputs,the device displays a preview user interface object that corresponds tothe first user interface object (e.g., a quick action menu thatcorresponds to an application launch icon, a preview of an email messagethat corresponds to an email item in a listing of email items, a previewof a photo that corresponds to a thumbnail image of the photo, etc.).This is illustrated in FIGS. 12J-12L, for example, where quick actionmenu 1230 and mini application object 1228 are displayed in response toa light press input. After showing the visual effect to indicate that anobject is intensity-reactive, providing object-specific responses inresponse to an intensity-based input (e.g., the intensity of the contactexceeds a threshold that is greater than the contact detection intensitythreshold) enhances the operability of the device and makes theuser-device interface more efficient (e.g., by avoiding user confusion,helping the user to achieve an intended result by providing the requiredinputs, and reducing user mistakes when operating/interacting with thedevice).

In some embodiments, in response to detecting the increase in thecharacteristic intensity of the contact above the first intensitythreshold: in accordance with a determination that the first userinterface object does not have differentiated responses tointensity-based inputs: the device provides (2220) predefined (e.g.,non-object-specific) failure feedback (e.g., a canned failure animationor tactile/audio output) to indicate that the device has detected anintensity-based input by the contact that does not have a correspondingobject-specific response. This is illustrated in FIG. 12H, for example.In some embodiments, the device does not provide any failure feedback(or any object-specific feedback) and the absence of the feedback to theinput indicates that the first user interface object does not have acorresponding object-specific response to the intensity-based input bythe contact. After showing the visual effect to indicate that an objectis non-intensity-reactive or not showing any visual effect to indicatethat the object is non-intensity-reactive, providing ageneric/predefined non-object-specific response in response to anintensity-based input enhances the operability of the device and makesthe user-device interface more efficient (e.g., by avoiding userconfusion, helping the user to achieve an intended result by providingthe required inputs, and reducing user mistakes whenoperating/interacting with the device).

In some embodiments, in response to detecting the increase in thecharacteristic intensity of the contact above the first intensitythreshold: in accordance with a determination that the first userinterface object has differentiated responses to intensity-based inputs:the device displays (2222) a precursor image of the preview userinterface object while detecting the decrease in the hover proximityparameter of the input object and while detecting the increase in thecharacteristic intensity of the contact by the input object with thetouch-sensitive surface. This is illustrated in FIG. 12K, for example,where a precursor image (e.g., preview platter 1206) is displayed. Aftershowing the visual effect to indicate that an object isintensity-reactive, providing visual feedback (e.g., a precursor imageof the preview user interface) in response to detecting an increase inintensity of the contact (e.g., before the intensity of the contactexceeds a threshold that is greater than the contact detection intensitythreshold) enhances the operability of the device and makes theuser-device interface more efficient (e.g., by informing the user of thestate of the device, avoiding user confusion, helping the user toachieve an intended result by providing the required inputs, andreducing user mistakes when operating/interacting with the device).

In some embodiments, displaying the precursor image of the preview userinterface object includes (2224): dynamically varying an appearance ofthe precursor image in accordance with the hover proximity parameter ofthe input object before the input object makes contact with thetouch-sensitive surface; dynamically varying the appearance of theprecursor image in accordance with the characteristic intensity of thecontact while the input object maintains contact with thetouch-sensitive surface; displaying a smooth transition (as opposed to adiscrete or abrupt transition) in the appearance of the precursor imagewhen the input object makes contact with the touch-sensitive surface;and displaying a continuous transformation from the precursor image tothe preview user interface object when the characteristic intensity ofthe contact increases above the first intensity threshold. After showingthe visual effect to indicate that an object is intensity-reactive,dynamically varying visual feedback (e.g., dynamically varying aprecursor image of the preview user interface) in accordance with thechanges in the intensity of the contact (e.g., before the intensity ofthe contact exceeds a threshold that is greater than the contactdetection intensity threshold) and smoothly transitioning the precursorimage to the preview user interface when the threshold intensity isreached enhance the operability of the device and make the user-deviceinterface more efficient (e.g., by informing the user of the state ofthe device, avoiding user confusion, helping the user to achieve anintended result by providing the required inputs, and reducing usermistakes when operating/interacting with the device).

In some embodiments, while displaying the preview user interface objectthat corresponds to the first user interface object in response todetecting the increase in the characteristic intensity of the contactabove the first intensity threshold and in accordance with thedetermination that the first user interface object has differentiatedresponses to intensity-based inputs, the device detects (2226) the inputobject breaking contact with the touch-sensitive surface. In response todetecting the input object breaking contact with the touch-sensitivesurface: in accordance with a determination that the input object meetssecond hover proximity criteria (e.g., the same as the first hoverproximity criteria or has a greater or lesser hover proximity range thanthe first hover proximity criteria), the device maintains display of thepreview user interface object while the input object continues to meetthe second hover proximity criteria; and in accordance with adetermination that the input object no longer meets the second hoverproximity criteria because the input object has exited a hover proximityrange specified by the second hover proximity criteria, the deviceceases to display the preview user interface object. This is illustratedin FIGS. 12M-12P, for example. Maintaining display of the preview userinterface after lift-off of the contact and before the input object islifted out of the hover proximity range enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byinforming the user of the state of the device, helping the user toachieve an intended result by providing the required inputs, andreducing user mistakes when operating/interacting with the device).

In some embodiments, maintaining display of the preview user interfaceobject while the input object continues to meet the second hoverproximity criteria includes (2228): dynamically varying an appearance ofthe preview user interface object in accordance with a current hoverproximity parameter of the input object while the input object continuesto meet the second hover proximity criteria (e.g., varying a size orappearance of the preview, and/or varying an amount of blurring that isapplied to the rest of the user interface around the preview, and/orvarying the z-height of the preview above the original z-plane of thepreview, or varying the brightness of the highlighting or the spot lightshone on the preview, and/or otherwise varying the amount of changesthat is applied to the appearance of the preview, in accordance with thecurrent hover distance of the input object above the touch-screen whilethe input object is within the three dimensional reactive region of thefirst user interface object). This is illustrated in FIGS. 12M-12O, forexample. Dynamically varying the appearance of the preview userinterface while maintaining display of the preview user interface afterlift-off of the contact and before the input object is lifted out of thehover proximity range enhances the operability of the device and makesthe user-device interface more efficient (e.g., by informing the user ofthe state of the device, helping the user to achieve an intended resultby providing the required inputs, and reducing user mistakes whenoperating/interacting with the device).

In some embodiments, after detecting the input object breaking contactwith the touch-sensitive surface and while maintaining display of thepreview user interface object that corresponds to the first userinterface object, the device detects (2230) that the input object hasmade contact with the touch-sensitive surface again. In response todetecting that the input object has made contact with thetouch-sensitive surface again, the device continues to maintain displayof the preview user interface object (e.g., including restoring theappearance of the preview user interface object to the state before theinput object broke contact with the touch-sensitive surface). Allowingthe user to maintain display of the preview user interface afterlift-off of the contact by touching down again on the touch-sensitivesurface while the preview user interface is still displayed during thehovering out process (e.g., after first lift-off followed by a period ofhovering) enhances the operability of the device and makes theuser-device interface more efficient (e.g., by reducing the number ofinputs needed to perform a task, such as keeping the preview on thedisplay, helping the user to achieve an intended result by providing therequired inputs, and reducing user mistakes when operating/interactingwith the device). In some embodiments, instead of maintaining display ofthe preview user interface object, the device performs a function andceases to display the second user interface object, e.g., launch anapplication to a user interface that corresponds to an item at thelocation of the contact, or opening a content item and replacing thecurrent user interface with another user interface that displays thecontent.

It should be understood that the particular order in which theoperations in FIGS. 22A-22G have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 1500, 1600, 1700, 1800, 1900, 2000, 2100, 2300 and 2400) arealso applicable in an analogous manner to method 2100 described abovewith respect to FIGS. 22A-22G. For example, the contacts, gestures,input objects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described above with reference to method 2200 optionally haveone or more of the characteristics of the contacts, gestures, inputobjects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described herein with reference to other methods describedherein (e.g., methods 1500, 1600, 1700, 1800, 1900, 2000, 2100, 2300 and2400). For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 22A-22G are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, detection operation 2204, and display operation 2206 and 2210are, optionally, implemented by event sorter 170, event recognizer 180,and event handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

FIGS. 23A-23E are flow diagrams illustrating a method 2300 ofinteracting with a user interface object through proximity-based andcontact-based inputs in accordance with some embodiments. The method2300 is performed at an electronic device (e.g., device 300, FIG. 3, orportable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the electronic deviceincludes one or more first sensors to detect proximity of an inputobject (e.g., a finger or a stylus) above the touch-sensitive surface(e.g., proximity sensors (such as infrared sensors), capacitive sensorsin the touch sensitive surface, or cameras next to the touch-sensitivesurface) and one or more second sensors to detect intensities of contactof the input object with the touch-sensitive surface. In someembodiments, the one or more second sensors are different from the oneor more first sensors. In some embodiments, the one or more secondsensors are the same as the one or more first sensors. In someembodiments, the touch-sensitive surface and the display are integratedinto a touch-sensitive display. In some embodiments, the display is atouch-screen display and the touch-sensitive surface is on or integratedwith the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 2300 are, optionally,combined and/or the order of some operations is, optionally, changed.

Method 2300 relates to providing visual feedback to indicate which edgeof a content selection object (e.g., text selection box) will be movedin accordance with movement of an input object to change a size of thecontent selection object. Conventionally, it is often difficult toselect a respective edge of a content selection object with a contactwhen two edges of the content selection object are located near eachother. For example, the input object (e.g., a finger or stylus) mayblock the view of the two edges of the content selection object and/oraccidently select the wrong edge when the input object moves close tothe two edges on the touch-screen, which will, in some circumstances,cause input mistakes and require additional steps to correct the inputmistakes. In the method disclosed herein, visual feedback that clearlyindicates which one of the edges is selected (or will be selected) forrelocation is provided when the input object is detected hovering overone or both of the edges (and optionally, before the requirement forselecting and moving the edge is met). If, upon seeing the visualfeedback, the user decides that the wrong edge is selected (or will beselected) for relocation, the user can adjust the hover location of theinput object to cause the correct edge to be selected. Providing visualfeedback to indicate which edge is selected (or is to be selected) forsubsequent movement before the actual movement is started enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to achieve an intended result byproviding the required inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

The device displays (2302) a content selection object (e.g., a textselection box, or object selection box) within selectable content,wherein the content selection object includes a first edge of thecontent selection object and a second edge of the content selectionobject, and wherein content (e.g., text) located between the first edgeof the content selection object and the second edge of the contentselection object is selected. The device detects (2304) a first portionof an input by the input object, including detecting the input object ata first hover location above the touch-sensitive surface thatcorresponds to the first edge of the content selection object. Inresponse to detecting the first portion of the input by the inputobject: in accordance with a determination that the first portion of theinput meets first criteria (e.g., edge-disambiguation criteria), whereinthe first criteria (e.g., edge-disambiguation criteria) require that theinput object meets hover proximity criteria when the input object isdetected at the first hover location above the touch-sensitive surfacethat corresponds to the location of the first edge of the contentselection object on the display in order for the first criteria to bemet, the device changes (2306) (e.g., visually enhancing) an appearanceof the first edge relative to the second edge of the content selectionobject in a first manner (e.g., enlarging a size of the first edgerelative to the second edge, changing the color of the first edgerelative to the second edge, enlarging a portion of the first edge,animating the first edge while keeping the second edge still, displayinga shadow or ghost cursor next to the first edge to indicate that thefirst edge of lifted toward the user relative to the second edge, etc.)to indicate that the first edge of the content selection object will beselected for movement relative to the second edge of the contentselection object when the input object meets second criteria (e.g.,edge-move criteria) (e.g., when lateral movement of the input object isdetected after the first criteria are met, or after augmented firstcriteria (e.g., first criteria and an additional criterion regarding thefirst criteria) are met). This is illustrated in FIGS. 13A-13C, forexample, where edge 1308 is selected for movement.

In some embodiments, in response to detecting the first portion of theinput by the input object: in accordance with a determination that thefirst portion of the input does not meet the first criteria (e.g.,edge-disambiguation criteria), the device maintains (2308) theappearance of the first edge relative to the second edge of the contentselection object to indicate that the selectable content will bescrolled when the input object meets the second criteria (e.g.,content-scroll criteria) (e.g., when lateral movement of the inputobject is detected without the first criteria having been met, orwithout the augmented first criteria having been met). This isillustrated in FIGS. 13H-13I, where content is scrolled, for example.The absence of changes to the appearance of the edges when neither isselected or to be selected for movement relative to the other is used asvisual feedback to indicate that the selectable content will be scrolledas a whole. If, upon seeing the absence of the visual feedback, the userdecides that an edge should be selected for relocation, the user canadjust the hover location of the input object to cause the correct edgeto be selected. Utilizing the absence of visual feedback to convey onestate of the device relative to another state for which visual feedbackis provided enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended result by providing the required inputs and reducinguser mistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, after detecting the first portion of the input, thedevice detects (2310) a second portion of the input by the input object,including detecting lateral movement of the input object. In response todetecting the second portion of the input object: in accordance with adetermination that the second portion of the input meets the secondcriteria (e.g., the edge-action criteria): in accordance with adetermination that the input object has met the first criteria (e.g.,edge-disambiguation criteria) during the first portion of the input, thedevice moves the first edge of the content selection object relative tothe second edge of the content selection object in accordance with thelateral movement of the input object across the touch-sensitive surface.In accordance with a determination that the input object has not met thefirst criteria (e.g., edge-disambiguation criteria) during the firstportion of the input, the device scrolls the selectable content inaccordance with the lateral movement of the input object across thetouch-sensitive surface. This is illustrated in FIGS. 13A-13E, and13H-13J, for example. Disambiguating a movement input as either a scrollinput or a resize input based on whether an edge of the contentselection object has previously been selected by an input objectenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by reducing the number of inputsrequired for a performing a task, helping the user to achieve anintended result by providing the required inputs, and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the second criteria (e.g., the edge-actioncriteria) require (2312) that the input object makes contact with thetouch-sensitive surface and maintains continuous contact with thetouch-sensitive surface while making the lateral movement across thetouch-sensitive surface in order for the second criteria to be met.Requiring the input object to make contact and maintain contact with thetouch-sensitive surface while making the lateral movement across thetouch-sensitive surface in order to move an edge of the contentselection object to resize the content selection object enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by avoiding accidental resizing of the contentselection object and reducing user mistakes when operating/interactingwith the device) which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, while the appearance of the first edge is changed(e.g., visually enhanced) relative to the second edge in the firstmanner, the device detects (2314) a first contact of the input objectwith the touch-sensitive surface at a location that corresponds to thefirst edge of the content selection object (while the first edge hasinput focus). In response to detecting the first contact of the inputobject with the touch-sensitive surface at the location that correspondsto the first edge of the content selection object: the device changes(e.g., visually enhancing) the first edge of the content selectionobject relative to the second edge of the content selection object in asecond manner that is distinct from the first manner (e.g., changing thecolor of the lollipop on the first edge, further enlarge the end of thelollipop, etc.). This is shown in FIGS. 12C and 12D, for example.Providing different visual feedback (e.g., changing the appearance ofthe first edge in different manners relative to the second edge) whenthe input object hovers over and makes contact with the touch-sensitivesurface enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by informing the user of the state ofthe device, helping the user to achieve an intended result by providingthe required inputs, and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while the appearance of the first edge is changed(e.g., visually enhanced) in the second manner, the device detects(2314) lift-off of the first contact from the touch-sensitive surface.In response to detecting the lift-off of the first contact from thetouch-sensitive surface: the device ceases to change (e.g., visuallyenhance) the appearance of the first edge in the second manner. Inaccordance with a determination that the input object meets the firstcriteria, the device changes (e.g., visually enhancing) the appearanceof the first edge in the first manner relative to the second edge. Inaccordance with a determination that the input object does not meet thefirst criteria, the device restores the appearance of the first edgerelative to the second edge of the content selection object. This isillustrated in FIGS. 13E-13G, where the changes to selection handle 1308is reversed as finger 734 is lifted off the touch-screen and lifted outof the hover proximity range above the touch-screen. Reversing thevisual changes applied to the first edge (e.g., reversing to changingthe appearance in the first manner, or completely removing the changespreviously applied) in accordance with whether the input objectcontinues to hover over the first edge or is lifted out of the hoverrange above the first edge enhances the operability of the device andmakes the user-device interface more efficient (e.g., by informing theuser of the internal state of the device, helping the user to achieve anintended result by providing the required inputs, and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the second criteria require (2318) that the inputobject makes the lateral movement above the touch-sensitive surfacewhile continuing to meet the hover proximity criteria in order for thesecond criteria to be met. Requiring the input object to remain in thehovering state while making the lateral movement over thetouch-sensitive surface in order to move an edge of the contentselection object to resize the content selection object enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by allowing the user to cancel the move by lifting awaythe input object without first making contact with the touch-sensitivesurface and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, after detecting the first portion of the input, thedevice detects (2320) a second portion of the input by the input object,including detecting lateral movement of the input object. In response todetecting the second portion of the input object: in accordance with adetermination that the second portion of the input meets the secondcriteria (e.g., the edge-action criteria) and that the input object hasmet the first criteria (e.g., edge-disambiguation criteria) during thefirst portion of the input, the device moves the first edge of thecontent selection object relative to the second edge of the contentselection object in accordance with the lateral movement of the inputobject. In accordance with a determination that the second portion ofthe input meets the second criteria (e.g., the edge-action criteria) andthat the input object has not met the first criteria (e.g.,edge-disambiguation criteria) during the first portion of the input, thedevice forgoes moving the first edge of the content selection object(and optionally, moving a cursor within the content while maintainingdisplay of the content selection object). Requiring the input object tomeet edge-disambiguation criteria before a resizing operation by lateralmovement of the input object enhances the operability of the device andmakes the user-device interface more efficient (e.g., by avoidingaccidental resizing of the content selection object and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

after detecting the second portion of the input by the input object andmoving the first edge relative to the second edge in response to thesecond portion of the input, the device detects (2322) a third portionof the input by the input object, including detecting that the inputobject no longer meets the hover proximity criteria. In response todetecting the third portion of the input by the input object: inaccordance with a determination that the input object no longer meetsthe hover proximity criteria because the input object has exited a hoverproximity range above the touch-sensitive surface, the device restoresthe first edge of the selection object to the location of the first edgebefore the first edge was moved in accordance with the lateral movementof the input object across the touch-sensitive surface (e.g., the changeto the content selection object is canceled when the user lift away theinput object without making contact with the touch-sensitive surface);and in accordance with a determination that the input object no longermeets the hover proximity criteria because the input object has madecontact with the touch-sensitive surface, the device confirms contentselection between the first edge and the second edge of the contentselection object (e.g., upon detecting subsequent lift-off of the inputobject from the touch-sensitive surface or upon detecting subsequentexit of the hover proximity range above the touch-sensitive surface bythe input object, the device will continue to maintain the selection,and optionally display a menu (e.g., with options for cut, copy, paste,lookup, etc.) with the selection). This is illustrated in FIGS. 13J-13N,for example. After moving first edge in accordance with the lateralmovement of the input object, allowing the user to confirm the move bymaking contact with the touch-sensitive surface or cancel the move bylifting the input object out of the hover proximity range without makingcontact with the touch-sensitive surface first enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,helping the user to achieve an intended result by providing the requiredinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the first criteria (e.g., the edge-disambiguationcriteria) further require (2324) that the input object meets the hoverproximity criteria for at least a first threshold amount of time withless than a threshold amount of movement away from the first hoverlocation in order for the first criteria to be met (e.g., the firstcriteria require that the input object is held substantially stationarywhile hovering over the first edge in order to select the first edge forsubsequent movement relative to the second edge). This is illustrated inFIGS. 13A-13C, for example, where finger 734 is hovered over selectionhandle 1308 for at least a threshold amount of time T before selectionhandle 1308 is selected for movement. Requiring the input object to meeta hover-hold requirement before performing a resizing operation bylateral movement of the input object enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byavoiding accidental resizing of the content selection object andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the first criteria further require (2326) that theinput object makes a predefined gesture (e.g., an in-air wiggle gesturethat includes movement of the input object back and forth over a portionof the touch-sensitive surface while remaining within a range of hoverdistance from the touch-sensitive surface) while the input object meetsthe hover proximity criteria at the first hover location in order forthe first criteria to be met. Requiring the detection of a predefinedgesture while the input object is hovering over the touch-sensitivesurface before performing a resizing operation by lateral movement ofthe input object enhances the operability of the device and makes theuser-device interface more efficient (e.g., by avoiding accidentalresizing of the content selection object and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, changing (e.g., visually enhancing) the appearanceof the first edge of the content selection object relative to the secondedge of the content selection object in the first manner includes (2328)transforming the first edge of the content selection object to a contentselection handle (e.g., a straight stem with an enlarged circular end)(while keeping a corresponding end of the second edge of the contentselection object unchanged (e.g., without any content selectionhandle)). Requiring the input object to meet a hover-hold requirementbefore performing a resizing operation by lateral movement of the inputobject enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by avoiding accidental resizing of thecontent selection object and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, changing (e.g., visually enhancing) the appearanceof the first edge of the content selection object relative to the secondedge of the content selection object in the first manner includes (2330)displaying a content selection handle adjacent to the first edge of thecontent selection object (e.g., such that the first edge is attached tothe content selection handle when the content selection handle isdragged by the input object across the display) (without concurrentlydisplaying a lollipop adjacent to the second edge of content selectionobject). Displaying the content selection handle adjacent to theselected edge enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended result by providing the required inputs and reducinguser mistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the first edge of the content selection object is(2332) a first content selection handle and the second edge of thecontent selection object is a second content selection handle other thanthe first content selection handle. Changing (e.g., visually enhancing)the appearance of the first edge of the content selection objectrelative to the second edge of the content selection object in the firstmanner includes enlarging at least a portion of the first contentselection handle (e.g., the round head of the content selection handle)relative to a corresponding portion of the second content selectionhandle. In some embodiments, the first content selection handle and thesecond content selection handle have the same original color, andvisually enhancing the appearance of the first edge relative to thesecond edge includes changing a color of the first content selectionhandle relative to an original color of the first content selectionhandle and the second content selection handle. This is illustrated inFIGS. 13B-13C, for example. Enlarging at least a portion of the selectedcontent selection handle relative to the unselected content selectionhandle enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended result by providing the required inputs and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

It should be understood that the particular order in which theoperations in FIGS. 23A-23E have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 1500, 1600, 1700, 1800, 1900, 2000, 2100, 2200 and 2400) arealso applicable in an analogous manner to method 2300 described abovewith respect to FIGS. 23A-23E. For example, the contacts, gestures,input objects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described above with reference to method 2300 optionally haveone or more of the characteristics of the contacts, gestures, inputobjects, user interface objects, tactile outputs, audio outputs,intensity thresholds, position indicators, focus selectors, andanimations described herein with reference to other methods describedherein (e.g., methods 1500, 1600, 1700, 1800, 1900, 2000, 2100, 2200 and2400). For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 23A-23E are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, detection operation 2304 and changing operation 2306 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

FIGS. 24A-24E are flow diagrams illustrating a method 2400 ofinteracting with a user interface object through proximity-based andcontact-based inputs in accordance with some embodiments. The method2400 is performed at an electronic device (e.g., device 300, FIG. 3, orportable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the electronic deviceincludes one or more first sensors to detect proximity of an inputobject (e.g., a finger or a stylus) above the touch-sensitive surface(e.g., proximity sensors (such as infrared sensors), capacitive sensorsin the touch sensitive surface, or cameras next to the touch-sensitivesurface) and one or more second sensors to detect intensities of contactof the input object with the touch-sensitive surface. In someembodiments, the one or more second sensors are different from the oneor more first sensors. In some embodiments, the one or more secondsensors are the same as the one or more first sensors. In someembodiments, the touch-sensitive surface and the display are integratedinto a touch-sensitive display. In some embodiments, the display is atouch-screen display and the touch-sensitive surface is on or integratedwith the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 2400 are, optionally,combined and/or the order of some operations is, optionally, changed.

Method 2400 relates to a heuristic for keeping input focus on a userinterface object stable against accidental movement of an input objectabove the user interface object. Specifically, after input focus isplaced on a first user interface object in response to detecting theinput object at a first hover location above the first user interfaceobject, the device compares subsequent movement (e.g., accidentalmovement or intentional movement) of the input object away from thefirst hover location (or from another stationary reference location thatis associated with the first user interface object (e.g., the centroidof the first user interface object)) against a variable movementthreshold in order to determine whether to maintain input focus on thefirst user interface object or to shift the input focus to another userinterface object. The variable movement threshold has a value that isdynamically determined based on a characteristic hover proximityparameter of the input object during the movement of the input objectaway from the first hover location. The characteristic hover proximityparameter of the input object during the hover movement of the inputobject is used as an indicator of whether the movement is likely to beintentional or accidental. For example, a smaller hover distance or afaster rate of change in the hover distance during the hover movementmay indicate that the movement is an accidental movement and that thedevice should require a larger movement in order to shift input focusfrom the first input object. Other factors may also be taken intoaccount in conjunction with the characteristic hover proximity parameterof the input object when determining whether to shift input focus awayfrom the first user interface object. Providing a more intelligent andrefined way of determining whether to maintain input focus on a userinterface object (e.g., by taking into account a characteristic hoverproximity parameter of the input object during hover movement of theinput object) enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended result by providing the required inputs and reducinguser mistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user of to use the device more quickly andefficiently.

The device displays (2402) a plurality of user interface objects on thedisplay, wherein the plurality of user interface objects include a firstuser interface object and a second user interface object, and whereinthe first user interface object and the second user interface object aredisplayed at different locations (e.g., separated by a first non-zerodistance) on the display. The device detects (2404) the input object ata first hover location above (e.g., directly above) a first portion ofthe touch-sensitive surface while the input object meets hover proximitycriteria (e.g., the input object is within a threshold hover distanceabove the touch-sensitive surface, or the hover proximity parameter ofthe input object is within a predetermined value range). In response todetecting the input object at the first hover location above the firstportion of the touch-sensitive surface while the input object meets thehover proximity criteria, the device places (2406) input focus on thefirst user interface object (e.g., shifting input focus from anotheruser interface object to the first user interface object or startinginput focus on the first user interface object when no other object hadinput focus). While the first user interface object has input focus andwhile the input object continues to meet the hover proximity criteria,the device detects (2406) a respective movement (e.g., a movement with alateral component and an optional vertical component) of the inputobject from the first hover location above the first portion of thetouch-sensitive surface to a respective hover location above (e.g.,directly above) a respective portion of the touch-sensitive surface thatis different from the first portion of the touch-sensitive surface. Inresponse to detecting the respective movement of the input object whilethe input object continues to meet the hover proximity criteria: inaccordance with a determination that the respective movement is a firstmovement from the first hover location to a second hover location thatis above a second portion of the touch-sensitive surface: in accordancewith a determination that the first movement meets firstfocus-maintenance criteria, wherein the first focus-maintenance criteriarequire that the first movement includes less than a first thresholdamount of lateral movement in order for the first focus-maintenancecriteria to be met, and wherein the first threshold amount of lateralmovement is determined based on a value of a characteristic hoverproximity parameter of the input object during the first movement of theinput object from the first hover location to the second hover location,the device maintains (2410) input focus on the first user interfaceobject; and in accordance with a determination that the first movementmeets first focus-shifting criteria, wherein the first focus-shiftingcriteria require that the first movement includes at least the firstthreshold amount of lateral movement in order for the firstfocus-shifting criteria to be met, the device shifts input focus fromthe first user interface object to the second user interface object.This is illustrated in FIGS. 14A-14G, for example. In some embodiments,each user interface object has a respective three-dimensional reactiveregion above the portion of the touch-sensitive surface that correspondsto the user interface object, and if no other user interface objectalready has input focus, an input object detected within the respectivethree-dimensional reactive region for the second user interface objectwould normally give input focus to the second user interface object.However, when the first user interface object and the second userinterface object are spaced close together, and the first user interfaceobject already has input focus, more lateral movement is required toshift the input focus away from the first user interface object to thesecond user interface object. Specifically, it is insufficient to havethe input object be detected within the reactive region above the seconduser interface object as a result of the movement of the input object,it is further required that the input object has made more than athreshold amount of lateral movement in order to shift the input focusfrom the first user interface object to the second user interfaceobject. Furthermore, the threshold amount of lateral movement isdetermined based on the characteristic hover proximity parameter of theinput object during the movement. In other words, the input focus on thefirst user interface object is made more stable by this additionalrequirement on the lateral movement of the input object.

In some embodiments, if the input object hovers over the second portionof the touch-sensitive surface when no other user interface object hadinput focus, the device places (2412) the input focus on the second userinterface object. When the focus-maintenance criteria are met when theinput object hovers over the second portion of the touch-sensitivesurface, the input focus remains with the first user interface object,and when the first input object did not already have input focus, thesecond user interface object obtains the input focus when the inputobject hovers over the second portion of the touch-sensitive surface. Byoverriding the default rule for granting input focus on an object whenanother object already has input focus, the device makes the input focusmore stable against accidental movement during a hover input, therebyenhancing the operability of the device and making the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended result by providing the required inputs and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, in response to detecting the respective movement ofthe input object while the input object continues to meet the hoverproximity criteria: in accordance with a determination that therespective movement is a second movement from the first hover locationto a third hover location that is above (e.g., directly above) a thirdportion of the touch-sensitive surface: in accordance with adetermination that the second movement meets second focus-maintenancecriteria, wherein the second focus-maintenance criteria require that thesecond movement includes less than a second threshold amount of lateralmovement (e.g., the second threshold amount of lateral movement issmaller than the first threshold amount of lateral movement) in orderfor the second focus-maintenance criteria to be met, the devicemaintains (2414) input focus on the first user interface object withoutregard to a value of the characteristic hover proximity parameter of theinput object during the second movement of the input object from thefirst hover location to the third hover location (e.g., the secondthreshold amount of lateral movement is independent of a value of thecharacteristic hover proximity parameter of the input object during thesecond movement of the input object from the first hover location to thethird hover location). By having a second set of focus-maintenancecriteria that are met when the input object makes very small movementsduring hover, the device makes the input focus more stable againstaccidental movement during a hover input, thereby enhancing theoperability of the device and making the user-device interface moreefficient (e.g., by helping the user to achieve an intended result byproviding the required inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, in response to detecting the respective movement ofthe input object while the input object continues to meet the hoverproximity criteria: in accordance with a determination that therespective movement is a third movement from the first hover location toa fourth hover location that is above (e.g., directly above) a fourthportion of the touch-sensitive surface: in accordance with adetermination that the third movement meets second focus-shiftingcriteria, wherein the second focus-shifting criteria require that thefourth portion of the touch-sensitive surface corresponds to a thirduser interface object of the plurality of user interface object, andthat the third movement includes at least a third threshold amount oflateral movement (e.g., the third threshold amount of lateral movementis greater than the first threshold amount of lateral movement), inorder for the second focus-shifting criteria to be met, the deviceshifts (2416) input focus from the first user interface object to thethird user interface object without regard to a value of thecharacteristic hover proximity parameter of the input object during thethird movement of the input object from the first hover location to thefourth hover location (e.g., the third threshold amount of lateralmovement is independent of a value of the characteristic hover proximityparameter of the input object during the third movement of the inputobject from the first hover location to the fourth hover location). Whenthe first input object makes a sufficient amount of lateral movementduring hover, the device takes input focus away from the first userinterface object, thereby enhancing the operability of the device andmaking the user-device interface more efficient (e.g., performing anoperation in accordance with user expectation and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the characteristic hover proximity parameter of theinput object is (2418) based on a hover distance (or its equivalent) ofthe input object from the touch-sensitive surface (and accordingly, insome embodiments, the first threshold amount of lateral movement (whichis not the actual lateral movement executed by the input object) isdetermined based on the vertical distance of the input object from thetouch-sensitive surface during the first movement from the first hoverlocation to the second hover location). This is illustrated in FIGS.14E-14G, for example.

In some embodiments, the characteristic hover proximity parameter of theinput object is (2420) based on a rate of change in a hover distance (orits equivalent) of the input object from the touch-sensitive surface(and accordingly, in some embodiments, the first threshold amount oflateral movement (which is not the actual lateral movement executed bythe input object) is determined based on a rate of change in thevertical distance of the input object from the touch-sensitive surfaceduring the first movement from the first hover location to the secondhover location). Using the rate of change in a hover distance of theinput object as a parameter to determine how much lateral movement isrequired to shift input focus away from the first user interface objectenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by avoiding accidentally shifting inputfocus from an object during touch-down or lift-away processes and byreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the first threshold amount of lateral movement is(2422) smaller for a greater characteristic hover proximity parameter ofthe input object (e.g., as a result, the input focus on the first objectis more stable when the input object is hovered lower over thetouch-sensitive surface, and it takes more lateral movement to shiftinput focus away from the first user interface object when the inputobject is located closer to the touch-sensitive surface). This isillustrated in FIGS. 14D-14G, for example. For example, the firstthreshold amount of lateral movement decreases through a series ofvalues as the input object moves toward the touch-sensitive surfaceand/or decreases through a series of values as the input object movesmore slowly and, optionally, the first threshold amount of lateralmovement increases through a series of values as the input object movesaway from the touch-sensitive surface and/or increases through a seriesof values as the input object moves more quickly. Requiring a smalleramount of lateral movement to shift input focus when the input object isfarther away from the touch-sensitive surface enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by avoiding accidentally shifting input focus from an object whenhovering close to the touch-sensitive surface and by reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the first threshold amount of lateral movement is(2424) greater for a greater characteristic hover proximity parameter ofthe input object (e.g., as a result, the input focus on the first objectis more stable when the input object is hovered higher over thetouch-sensitive surface, and it takes more lateral movement to shiftinput focus away from the first user interface object when the inputobject is located farther away from the touch-sensitive surface). Forexample, the first threshold amount of lateral movement increasesthrough a series of values as the input object moves toward thetouch-sensitive surface and/or increases through a series of values asthe input object moves more slowly and, optionally, the first thresholdamount of lateral movement decreases through a series of values as theinput object moves away from the touch-sensitive surface and/ordecreases through a series of values as the input object moves morequickly. Requiring a greater amount of lateral movement to shift inputfocus when the input object is farther away from the touch-sensitivesurface enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by avoiding accidentally shifting inputfocus from an object when hovering farther away from the touch-sensitivesurface and by reducing user mistakes when operating/interacting withthe device) which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, in accordance with a determination that the inputobject is moving toward the touch-sensitive surface, the devicemaintains (2426) input focus on the first user interface object for atleast a predetermined amount of time (e.g., for long enough to determinewhether the user is tapping on the touch-sensitive surface to confirmselection of the highlighted user interface object) (e.g., as a result,the input focus on the first object is more stable when the input objectis moving quickly toward the touch-sensitive surface (e.g., during atap), and it is less likely to accidentally lose input focus on thefirst user interface object during a tap input on the first userinterface object). This is illustrated in FIGS. 14K-14L, for example.Maintaining input focus for a predetermined amount of time when theinput object is moving toward the touch-sensitive surface enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by avoiding accidentally shifting input focus from anobject during a touch-down process and by reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the device detects (2428) that the input objectmeets information-object-display criteria, wherein theinformation-object-display criteria require that the input object meetsthe hover proximity criteria in order for the information-object-displaycriteria to be met. In response to detecting that the input object meetsthe information-object-display criteria, the device displays aninformation-display object (e.g., an information pop-up) thatcorresponds to the input object, including: in accordance with adetermination that a respective user interface object (e.g., arespective POI represented by a corresponding pin on a map) of theplurality of user interface objects (e.g., a plurality of points ofinterests (POIs) represented by corresponding pins on the map) has inputfocus, displaying object-specific information (e.g., name, type, ratinginformation, location information, etc.) that corresponds to therespective user interface object of the plurality of user interfaceobject in the information-display object, and in accordance with adetermination that none of the plurality of user interface objects hasinput focus, forgoing display any object-specific information in theinformation-display object (e.g., displaying an empty pop-up ordisplaying generic information in the information pop-up that isapplicable to multiple user interface objects on the display (e.g., acluster of multiple pins on a map)). This is illustrated in FIGS. 14C(e.g., empty information pop-up 1412) and 14D (e.g., information pop-up1414 for location pin 1404), for example. Displaying object-specificinformation for a user interface object that has input focus during ahover input enhances the operability of the device and makes theuser-device interface more efficient (e.g., by providing information tothe user, helping the user to achieve an intended result by providingthe required inputs, and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the information-object-display criteria furtherrequire (2430) that the input object is hovering over a respectiveportion of the touch-sensitive surface that is within a threshold rangeof a location of at least one of the plurality of user interface objectson the display in order for the information-object-display criteria tobe met (e.g., the information pop-up is only displayed if the inputobject is hovering over a location that is sufficiently close to atleast one point of interest on the touch-screen). Displayingobject-specific information for a user interface object that is within athreshold range of the input object during a hover input enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by providing information to the user, informing theuser of the internal state of the device, helping the user to achieve anintended result by providing the required inputs, and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, while displaying the information-display object(e.g., the information pop-up), the device detects (2432) that the inputobject meets information-object-expansion criteria, wherein theinformation-object-expansion criteria require that the input objectmakes contact with the touch-sensitive surface while the respective userinterface object has input focus. In response to detecting that theinput object meets the information-object-expansion criteria, the devicedisplays additional object-specific information that corresponds to therespective user interface object (e.g., expanding the information pop-upto show more information on the point of interest that has input focus,or opening a webpage or window to show more information on the point ofinterest that has input focus). Expanding object-specific informationfor user input object when the input object makes contact with thetouch-sensitive surface enhances the operability of the device and makesthe user-device interface more efficient (e.g., by providing informationto the user, helping the user to achieve an intended result by providingthe required inputs, and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently. It should be understoodthat the particular order in which the operations in FIGS. 24A-24E havebeen described is merely an example and is not intended to indicate thatthe described order is the only order in which the operations could beperformed. One of ordinary skill in the art would recognize various waysto reorder the operations described herein. Additionally, it should benoted that details of other processes described herein with respect toother methods described herein (e.g., methods 1500, 1600, 1700, 1800,1900, 2000, 2100, 2200 and 2300) are also applicable in an analogousmanner to method 2400 described above with respect to FIGS. 24A-24E. Forexample, the contacts, gestures, input objects, user interface objects,tactile outputs, audio outputs, intensity thresholds, positionindicators, focus selectors, and animations described above withreference to method 2400 optionally have one or more of thecharacteristics of the contacts, gestures, input objects, user interfaceobjects, tactile outputs, audio outputs, intensity thresholds, positionindicators, focus selectors, and animations described herein withreference to other methods described herein (e.g., methods 1500, 1600,1700, 1800, 1900, 2000, 2100, 2200 and 2300). For brevity, these detailsare not repeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 24A-24E are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, detection operations 2404 and 2408, placing operation 2406, andshifting operation 2410 are, optionally, implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A computer readable storage medium storing one ormore programs, the one or more programs comprising instructions which,when executed by an electronic device with a touch-sensitive surface anda display, wherein the electronic device includes one or more sensors todetect proximity of an input object above the touch-sensitive surface,cause the electronic device to: display a user interface object at afirst location on the display and at least one additional user interfaceobject on the display; detect selection of the user interface object atthe first location on the display; and, while the user interface objectis selected: detect lateral movement of the input object over thetouch-sensitive surface while the input object meets hover criteria;and, in response to detecting lateral movement of the input object overthe touch-sensitive surface while the input object meets the hovercriteria: move the selected user interface object in accordance with thelateral movement of the input object over the touch-sensitive surface;and, while moving the selected user interface object in accordance withthe lateral movement of the input object over the touch-sensitivesurface, dynamically vary a first visual characteristic of the selecteduser interface object relative to the first visual characteristic of theat least one additional user interface object on the display, whereinthe amount by which the first visual characteristic of the selected userinterface object varies relative to the first visual characteristic ofthe at least one additional user interface object is determined inaccordance with a current hover proximity parameter of the input object.2. The storage medium of claim 1, wherein the hover criteria include acriterion that is met when the hover proximity parameter of the inputobject is less than a threshold proximity value.
 3. The storage mediumof claim 1, including instructions which, when executed by theelectronic device, cause the electronic device to: while the inputobject is detected, display a position indicator at a location on thedisplay that corresponds to a current position of the input object overthe touch-sensitive surface.
 4. The storage medium of claim 3, includinginstructions which, when executed by the electronic device, cause theelectronic device to: dynamically vary a visual characteristic of theposition indicator in accordance with the current hover proximityparameter of the input object.
 5. The storage medium of claim 1, whereindetecting selection of the user interface object includes detecting theinput object making and breaking contact with the touch-sensitivesurface at a location that corresponds to the first location of the userinterface object on the display.
 6. The storage medium of claim 1,wherein detecting selection of the user interface object includesdetecting a press input by the input object at a location thatcorresponds to the first location of the user interface object on thedisplay, and wherein detecting the press input includes detecting acharacteristic intensity of a contact of the input object with thetouch-sensitive surface above a first threshold intensity.
 7. Thestorage medium of claim 1, wherein detecting selection of the userinterface object includes detecting a long press input by the inputobject at a location that corresponds to the first location of the userinterface object on the display, and wherein detecting the long pressinput includes detecting a characteristic intensity of a contact of theinput object with the touch-sensitive surface remains above a firstthreshold intensity for at least a threshold amount of time.
 8. Thestorage medium of claim 1, including instructions which, when executedby the electronic device, cause the electronic device to: prior todetecting selection of the user interface object at the first locationand while the input object meets the hover criteria: detect the inputobject over a location on the touch-sensitive surface that correspondsto the first location of the user interface object on the display; and,while detecting the input object over the location on thetouch-sensitive surface that corresponds to the first location of theuser interface object on the display, dynamically vary an appearance ofthe user interface object at the first location in accordance with thecurrent hover proximity parameter of the input object; while dynamicallyvarying the appearance of the user interface object at the firstlocation, detect lateral movement of the input object over thetouch-sensitive surface; and, in response to detecting lateral movementof the input object over the touch-sensitive surface: cease todynamically vary the appearance of the user interface object at thefirst location; and, maintain the user interface object at the firstlocation.
 9. The storage medium of claim 1, including instructionswhich, when executed by the electronic device, cause the electronicdevice to: in response to detecting selection of the user interfaceobject at the first location on the display, provide visual feedback toindicate that the user interface object is selected.
 10. The storagemedium of claim 1, wherein dynamically varying the first visualcharacteristic of the user interface object in accordance with thecurrent hover proximity parameter of the input object includesdynamically changing a size of the user interface object in accordancewith the current hover proximity parameter of the input object.
 11. Thestorage medium of claim 1, including instructions which, when executedby the electronic device, cause the electronic device to: whiledynamically varying the first visual characteristic of the selected userinterface object, maintain display of all of the selected user interfaceobject on the display.
 12. An electronic device, comprising: a display;a touch-sensitive surface; one or more sensors to detect proximity of aninput object above the touch-sensitive surface; one or more processors;memory; and one or more programs, wherein the one or more programs arestored in the memory and configured to be executed by the one or moreprocessors, the one or more programs including instructions for:displaying a user interface object at a first location on the displayand at least one additional user interface object on the display;detecting selection of the user interface object at the first locationon the display; and, while the user interface object is selected:detecting lateral movement of the input object over the touch-sensitivesurface while the input object meets hover criteria; and, in response todetecting lateral movement of the input object over the touch-sensitivesurface while the input object meets the hover criteria: moving theselected user interface object in accordance with the lateral movementof the input object over the touch-sensitive surface; and, while movingthe selected user interface object in accordance with the lateralmovement of the input object over the touch-sensitive surface,dynamically varying a first visual characteristic of the selected userinterface object relative to the first visual characteristic of the atleast one additional user interface object on the display, wherein theamount by which the first visual characteristic of the selected userinterface object varies relative to the first visual characteristic ofthe at least one additional user interface object is determined inaccordance with a current hover proximity parameter of the input object.13. The electronic device of claim 12, including instructions for: whiledynamically varying the first visual characteristic of the selected userinterface object, maintaining display of all of the selected userinterface object on the display.
 14. The electronic device of claim 12,wherein the hover criteria include a criterion that is met when thehover proximity parameter of the input object is less than a thresholdproximity value.
 15. The electronic device of claim 12, includinginstructions for: while the input object is detected, displaying aposition indicator at a location on the display that corresponds to acurrent position of the input object over the touch-sensitive surface.16. The electronic device of claim 15, including instructions for:dynamically varying a visual characteristic of the position indicator inaccordance with the current hover proximity parameter of the inputobject.
 17. The electronic device of claim 12, wherein detectingselection of the user interface object includes detecting the inputobject making and breaking contact with the touch-sensitive surface at alocation that corresponds to the first location of the user interfaceobject on the display.
 18. The electronic device of claim 12, whereindetecting selection of the user interface object includes detecting apress input by the input object at a location that corresponds to thefirst location of the user interface object on the display, and whereindetecting the press input includes detecting a characteristic intensityof a contact of the input object with the touch-sensitive surface abovea first threshold intensity.
 19. The electronic device of claim 12,wherein detecting selection of the user interface object includesdetecting a long press input by the input object at a location thatcorresponds to the first location of the user interface object on thedisplay, and wherein detecting the long press input includes detecting acharacteristic intensity of a contact of the input object with thetouch-sensitive surface remains above a first threshold intensity for atleast a threshold amount of time.
 20. The electronic device of claim 12,including instructions for: prior to detecting selection of the userinterface object at the first location and while the input object meetsthe hover criteria: detecting the input object over a location on thetouch-sensitive surface that corresponds to the first location of theuser interface object on the display; and, while detecting the inputobject over the location on the touch-sensitive surface that correspondsto the first location of the user interface object on the display,dynamically varying an appearance of the user interface object at thefirst location in accordance with the current hover proximity parameterof the input object; while dynamically varying the appearance of theuser interface object at the first location, detecting lateral movementof the input object over the touch-sensitive surface; and, in responseto detecting lateral movement of the input object over the touch-sensitive surface: ceasing to dynamically vary the appearance of theuser interface object at the first location; and, maintaining the userinterface object at the first location.
 21. The electronic device ofclaim 12, including instructions for: in response to detecting selectionof the user interface object at the first location on the display,providing visual feedback to indicate that the user interface object isselected.
 22. The electronic device of claim 12, wherein dynamicallyvarying the first visual characteristic of the user interface object inaccordance with the current hover proximity parameter of the inputobject includes dynamically changing a size of the user interface objectin accordance with the current hover proximity parameter of the inputobject.
 23. A method, comprising: at an electronic device with atouch-sensitive surface and a display, wherein the electronic deviceincludes one or more sensors to detect proximity of an input objectabove the touch-sensitive surface: displaying a user interface object ata first location on the display; detecting selection of the userinterface object at the first location on the display and at least oneadditional user interface object on the display; and, while the userinterface object is selected: detecting lateral movement of the inputobject over the touch-sensitive surface while the input object meetshover criteria; and, in response to detecting lateral movement of theinput object over the touch-sensitive surface while the input objectmeets the hover criteria: moving the selected user interface object inaccordance with the lateral movement of the input object over thetouch-sensitive surface; and, while moving the selected user interfaceobject in accordance with the lateral movement of the input object overthe touch-sensitive surface, dynamically varying a first visualcharacteristic of the selected user interface object relative to thefirst visual characteristic of the at least one additional userinterface object on the display, wherein the amount by which the firstvisual characteristic of the selected user interface object variesrelative to the first visual characteristic of the at least oneadditional user interface object is determined in accordance with acurrent hover proximity parameter of the input object.
 24. The method ofclaim 23, further comprising: while dynamically varying the first visualcharacteristic of the selected user interface object, maintainingdisplay of all of the selected user interface object on the display. 25.The method of claim 23, wherein the hover criteria include a criterionthat is met when the hover proximity parameter of the input object isless than a threshold proximity value.
 26. The method of claim 23,further comprising: while the input object is detected, displaying aposition indicator at a location on the display that corresponds to acurrent position of the input object over the touch-sensitive surface.27. The method of claim 26, further comprising: dynamically varying avisual characteristic of the position indicator in accordance with thecurrent hover proximity parameter of the input object.
 28. The method ofclaim 23, wherein detecting selection of the user interface objectincludes detecting the input object making and breaking contact with thetouch- sensitive surface at a location that corresponds to the firstlocation of the user interface object on the display.
 29. The method ofclaim 23, wherein detecting selection of the user interface objectincludes detecting a press input by the input object at a location thatcorresponds to the first location of the user interface object on thedisplay, and wherein detecting the press input includes detecting acharacteristic intensity of a contact of the input object with thetouch- sensitive surface above a first threshold intensity.
 30. Themethod of claim 23, wherein detecting selection of the user interfaceobject includes detecting a long press input by the input object at alocation that corresponds to the first location of the user interfaceobject on the display, and wherein detecting the long press inputincludes detecting a characteristic intensity of a contact of the inputobject with the touch-sensitive surface remains above a first thresholdintensity for at least a threshold amount of time.
 31. The method ofclaim 23, further comprising: prior to detecting selection of the userinterface object at the first location and while the input object meetsthe hover criteria: detecting the input object over a location on thetouch-sensitive surface that corresponds to the first location of theuser interface object on the display; and, while detecting the inputobject over the location on the touch-sensitive surface that correspondsto the first location of the user interface object on the display,dynamically varying an appearance of the user interface object at thefirst location in accordance with the current hover proximity parameterof the input object; while dynamically varying the appearance of theuser interface object at the first location, detecting lateral movementof the input object over the touch-sensitive surface; and, in responseto detecting lateral movement of the input object over the touch-sensitive surface: ceasing to dynamically vary the appearance of theuser interface object at the first location; and, maintaining the userinterface object at the first location.
 32. The method of claim 23,further comprising: in response to detecting selection of the userinterface object at the first location on the display, providing visualfeedback to indicate that the user interface object is selected.
 33. Themethod of claim 23, wherein dynamically varying the first visualcharacteristic of the user interface object in accordance with thecurrent hover proximity parameter of the input object includesdynamically changing a size of the user interface object in accordancewith the current hover proximity parameter of the input object.